Hierarchy

⤷

⤷

⤷

Basic Data
Data Element | JV_BANK_TYPE |
Short Description | JV Business Partner's Bank type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BVTYP | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | BNKT | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 9 | Bank Type |
Medium | 19 | Partner's Bank Type |
Long | 20 | Operator's Bank Type |
Heading | 9 | Bank Type |
Documentation
Definition
Each bank type combined with the partner account (either customer account or vendor account) forms a unique entry for the bank information. This bank information (bank type + partner) can be used to derive the bank account needed for posting.
How to use it
When you want to enter several bank accounts into your partner master record, make sure that you also key in the bank type.
By the time you do a vendor (or customer) posting, key in the bank type field "Part.Bank" (BSEG-BVTYP) in the vendor (or customer) line item. The system will automatically derive the bank account using bank type and vendor (or customer) account.
When we need to enter it
If there is more than 1 bank accounts defined in the vendor master of the operator, the user is required to enter bank type in non-operated billing. Otherwise, by default, an error message will be issued.
However, if the user chooses to suppress this error message, the user can:
- Go into JVA Configuration -> Environment -> Maintain messages
- Type in "G4" in Application Area field.
- Search for the message in the list.
- If the message is found, enter the message type
(e => error, w => warning, - => switch off message)
for online processing, batch input processing, and standard processing. - If the message is not found, insert a new line for this message and enter the message types.
History
Last changed by/on | SAP | 20020108 |
SAP Release Created in |