Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
JBA (Package) Application developmnet IS-B General Development
Basic Data
| Data Element | JBXBIGEL |
| Short Description | Batch Input Docu.for Money Market |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 0 |
Documentation
Call
Transaction: se38
Program: RJBDBTC2
Parameters: File name (file path for data)
Batch input session
Filler for empty fields ('nodata' value)
Editing the batch input session:
System -> Services -> Batch input -> Edit
Function Scope
Create fixed-term deposit
General Information
Money market transactions comprise master data, administration data, conditions and additional flows.
Conditions and additional flows can have any number of entries. For this you can transfer 1..n records.
Normally 1..n additional flows are entered per transaction.
If you want to enter single dates for the condition type you also have to transfer single records.
Because of this structure, money market transactions are transferred in 1..n records.
Receiver Structure
The receiver structure (JBIUGEL) comprises the master data of the financial transaction (VTBFHA) and the condition and flow data.
With batch input transfer procedures, all data elements in the receiver structure must be of type CHARacter.
You can determine the definition and documentation for data elements via the required/optional control.
Sequence of Transfer
All data records in a money market transaction must be written to the sequential transfer file together.
Within the transaction, bear in mind that the master data is delivered first. This is followed by the conditions and additional flows,although the additional flow is an optional entry.
Use the required/optional control to determine which fields are required and which fields are optional.
The classification of a field as a required field is carried out in the online transaction.
Identification of master, condition and flow data
Fields
filled not filled
Master MANDT
BUKRS
Condition detail MANDT
SKOART BUKRS = nodata
Additional flow MANDT
SFHAZBA BUKRS = nodata
With the exception of the first data record for a transaction, the company code must always be filled with the 'nodata' character.
All fields whose content you do not want to transfer or which are assigned a value in the course of the transaction (e.g. a time stamp), must be filled with the 'nodata' value in order to transfer the data by batch input.
If, for example, you only want to transfer conditions or additional flows, you have to fill the master data with the 'nodata' value.
Special Considerations
With batch input procedures, the transaction is called up new for each Money Market deal (financial transaction). In the raw data, the new transactions can be recognized by the fact that the company code field (BUKRS) is filled.
Based on the company code, either internal or external number assignment is carried out for the transaction number.
When you create a money market transaction in the system, you initially have to fill out the following fields:
BUKRS
SGSART
SFHAART
KONTRH
RPORTB
If external number assignment is set in the company code for the transaction number, you must also transfer the transaction number (RFHA).
The business partner must be defined under the role category 'Treasury partner' together with the Money Market transaction authorization.
At present only one condition (nominal interest) can be transferred. To transfer several condition types, you have to carry out some program enhancements.
Use the 'nodata' value to transfer those fields whose contents you do not want to change in the course of the transaction; these fields either remain blank, retain their original content or are supplied with values (e.g. a time stamp) by the system.
In the batch input programs, the system checks each screen field for the 'nodata' character.
When you call up the batch input program, the 'nodata' value used in the raw data is entered as a parameter.
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in |
