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 | JBXBIDEV |
| Short Description | Batch Input Docu.for Foreign Exchange |
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: RJBDBTC1
When you call up the report you enter the file path for the raw data,
the name of the batch input session, and the nodata character (filler).
Processing the batch input session:
System -> Services -> Batch input -> Edit
Function Scope
Create spot/forward transaction
General Information
Forex transactions comprise master data, administration data, additional flows.
Additional flows can have any number of entries.
Normally 1..n additional flows are entered per transaction.
Because of this structure, forex transactions are transferred in 1..n records.
Receiver Structure
The receiver structure (JBIUDEV) comprises the master data of the financial transaction (VTBFHA) and the 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 forex 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 and flow data
Fields
filled not filled
Master MANDT
BUKRS
Additional flow MANDT BUKRS = nodata
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 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 forex 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 forex 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 forex transaction authorization.
To suppress warning messages, the fields Portfolio (RPORTB) and Account assignment reference (RREFKONT) are defined as required fields.
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 |
