Functionality
Function module VENDOR_BDCDATA generates data per transaction in batchinput format (data for input in a transaction or adialog sequence).
Parameter:

• Import parameters:

PI_VART: Processing type;
Characteristic = ' ': Calling the module occurs during the processingof change documents.
Characteristic = 'X': Calling the module occurs during full processingof a vendor; for example, due to sending or getting vendor data viaApplication Link Enabling (ALE).
You should always start the function module with the characteristic 'X'because then preliminary checks (e.g. whether a partner function hasbeen defined as a non-changeable mandatory partner function inCustomizing) take place during the processing of partner functions(BWYT3).
PI_FL_CHECK: Indicator - Only check data (parameter is optional)
Characteristic = 'X': For table parameter PI_TAB_WA data, the systemwill check whether there are requirements that would prevent datatransfer. No processing takes place; in particular, table parameterPE_TAB_FT is not generated.
Characteristic = ' ': No checks are carried out; table parameterPE_TAB_FT is generated.

• Export parameters: none


• Table parameters:

PI_TAB_WA: Input table with B structures (see below)
PE_TAB_FT: Output table with data in batch input format
PE_FEHL_WA: Output table; filled when error occured. It includesthe last processed record of table parameter PI_TAB_WA. (The parameteris optional.)
B structures:

• Information which applies to the complete batch input session is
defined in the session record.

• Information which applies to the whole transaction is defined in the
header record. This includes, for example, a transaction code and keyfields.

• For each vendor table for which batch input should be possible, a batch
input structure has been created in the Data Dictionary.
Each structure is identified by record type and possibly table name.
The individual structures include:

• BGR00 Record type 0 Session record


• BLF00 Record type 1 Header data


• BLFA1 Record type 2 General data


• BLFBK Record type 2 Bank details (including bank master data)


• BLFB1 Record type 2 Company code data


• BLFB5 Record type 2 Dunning data


• BLFM1 Record type 2 Purchasing data (purchasing organization level)


• BLFM2 Record type 2 Purchasing data (deviating data retention level)


• BLFLR Record type 2 Supply regions


• BWYT1 Record type 2 Vendor sub-range


• BWYT3 Record type 2 Partner functions

For each call, the function module generates batch input format dataand expects the following sequence for the input table data:
1 BGR00 record (record type 0)
1 BLF00 record (record type 1)
1..n data records (record type 2)
For the following central transactions, data is created in batch inputformat:

• XK01 Create Vendor


• XK02 Change Vendor


• XK05 Block/Unblock Vendor


• XK06 Mark for deletion Vendor

If, due to an error, the function module cannot generate data in batchinput format for a transaction, it terminates with an exception. Sinceexceptions are always issued with a message, you can issue the reasonfor termination with the help of system variables. The only time thisdoes not apply is for the exception 'MULTIPLE_TA' which is generated ifthe function module is to process data for more than one transaction.In this case, at least data for the first transaction will be in batchinput format in output table PE_TAB_FT.

Example
Report RMBIKR00