Ansicht
Dokumentation

RJLPBTCI - IS-M/SD: Batch Input Interface for Postal Charges

BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Description

The batch input report RV14BTCI is used to process condition records:

• Prices

• Surcharges and discounts

• Freight

• Taxes

Note

Structures

Data that applies to the entire batch input session is defined in the session header record.

Data that applies to an entire transaction is defined in the header data. This data includes the transaction code and key.

A batch input structure is created in the Data Dictionary for every condition table for which batch input is to be possible.

Each structure is identified by the record type, condition type and table name.

The structures are as follows:

• BGR00 Rec.type 0 Session header record

• BKOND1 Rec.type 1 Header data (tr.code, condition type, table name)

• BKOND2 Rec.type 2 Main data

• BKOND3 Rec.type 3 Scale data
  
  

It must be possible to distinguish for each field transferred to the batch input structure whether the value in the field is initial (e.g. field is to be reset to its initial value) or whether batch input is not necessary at all for this field. This means you do not need to define a symbol to perform the function "No batch input for this field". This symbol is "/" as default.

If you do not want to use the symbol "/", you can specify another symbol to perform this function in field BGR00-NODATA in the session header record.

Before the data is entered in the batch input structure, this symbol must be entered at the beginning of each field in the structures (except the session header record BGR00).

The fields in the structures reference the data elements assigned to the fields in the original tables. However, this does not apply to numeric and packed fields. These fields must be assigned their own CHAR data elements for batch input since packed fields cannot be preassigned a symbol. This means that amounts with a decimal point can be transferred to the interface.

Parameters

• REC_TR_M Max no.records per transaction (default: 100)
  This parameter determines the maximum number of condition records that are to be updated in a transaction. This can affect performance when the session is processed.
  You should only change the default value if problems arise with the main memory.
  

• KOND_MAX Max. no. cond. recs per screen (default: 10)
  This parameter allows you to control the maximum number of condition records that are visible on screen.
  You should only change (reduce) this parameter if problems arise when processing the session.
  

• STAF_MAX Max no. scales per screen (default: 10)
  This parameter allows you to control the maximum number of scale records that are visible on screen.
  You should only change (reduce) this parameter if problems arise when processing the session.
  

• REC_MAX Max. no. cond. recs in table (default: 500)
  This parameter indicates the maximum number of condition records that can be imported into the internal table. This can influence the amount of memory required to create the session. It is also possible to improve performance when processing the session with a higher value, which allows improved optimization.
  You should only change the default value if problems arise with the main memory.
  

Special fields in the session header record:

The session name (BGR00-GROUP) must be specified in the session header record. When a second session header record is transmitted, the current session is closed and a new one is opened.

The NODATA symbol can be transferred in the session header record (see above).

A blocking date (BGR00-START) can be transferred in the session header record. This date must be specified in the format 'YYYYMMDD'.

Transactions supported:

The following central transaction is supported in the current version:

• XK15 Create Condition (for applications V and M)

General Data in Customer Master   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 4503 Date: 20240531 Time: 144429     sap01-206 ( 69 ms )