SAP Function VENDOR_BDCDATA - Batch input: creditor

Parameter Reference Type Length Default Optional Text
PI_FL_CHECK RFPDO-RFBICHCK C 1 SPACE X Check batch input data only
PI_VART 0 ' ': Process. change doc., 'X' complete processing
PI_XK99_USED CHAR1 C 1 SPACE X

Parameter Reference Length Optional Text
PE_FEHL_WA BDIFIBIWA 2000 X Output table: faulty B structure
PE_TAB_FT BDCDATA 309 Output table with BDC data
PI_TAB_WA BDIFIBIWA 2000 Input table with B structures (BGR00, BLF00...)

Exception Text
BLF00_MISSING Transaction does not begin with header record (cat. 1)
BUKRS_NOT_IN_T079K Screen layout for company code not in table T079K
B_EXTENSION Customer still uses old B structure
EKORG_NOT_IN_T079M Screen layout for purchasing organization not in table T079M
INTERNAL_ERROR
INVALID_TAXGR
KTOKK_NOT_FOUND Account group does not exist in table T077K
MULTIPLE_BLFA1 Pass on BLFA1 data more than once
MULTIPLE_BLFB1 Pass on BLFB1 data more than once
MULTIPLE_BLFB5 Pass on BLFB5 data more than once
MULTIPLE_BLFM1 Pass on BLFM1 data more than once
MULTIPLE_TA Processing of several TA in one call
NODATA_INVALID Special character for NODATA not valid
NO_BKNVK_BEC_ENTRY
NO_BKNVK_BEC_EXIST
NO_BLFA1_BEC_EXIST BLFA1 data not processed because record exists
NO_BLFAT_BEC_ENTRY
NO_BLFAT_BEC_EXIST
NO_BLFB1_BEC_BUKRS BLFB1 data not processed, since company code missing
NO_BLFB5_BEC_BUKRS BLFB5 data not processed, since company code missing
NO_BLFB5_BEC_ENTRY BLFB5 data not processed because deletion or blocking table
NO_BLFBK_BEC_ENTRY BLFBK data not processed because deletion or blocking table
NO_BLFBK_BEC_ERASE No BLFBK processing because bank details are to be deleted
NO_BLFBK_BEC_EXIST1 BLFBK data not created because LFA1 exists
NO_BLFBK_BEC_EXIST2 No BLFBK processing because BNKA data already exists
NO_BLFBK_BEC_KEY1 No BLFBK processing because country key missing
NO_BLFBK_BEC_KEY2 No BLFBK processing because country key not in table T005
NO_BLFBW_BEC_BUKRS
NO_BLFBW_BEC_ENTRY
NO_BLFBW_SENTENCE
NO_BLFEI_BEC_EKORG
NO_BLFEI_BEC_ENTRY
NO_BLFLR_BEC_EKORG BLFLR data not processed because purchasing organization missing
NO_BLFLR_BEC_ENTRY BLFLR data not processed because blocking or deletion table
NO_BLFM1_BEC_EKORG BLFM1 data not processed because purchasing organization missing
NO_BLFM2_BEC_EKORG BLFM2 data not processed because purchasing organization missing
NO_BLFM2_BEC_ENTRY BLFM2 data not processed because blocking or deletion table
NO_BLFM2_LTSNR_WERKS BLFM2 data not processed because LTSNR and WERKS missing
NO_BWYT1_BEC_EKORG BWYT1 data not processed because purchasing organization missing
NO_BWYT1_BEC_ENTRY BWYT1 data not processed because blocking or deletion table
NO_BWYT3_BEC_EKORG BWYT3 data not processed because purchasing organization missing
NO_BWYT3_BEC_ENTRY BWYT3 data not processed because blocking or deletion table
NO_BWYT3_LTSNR_WERKS BWYT3 data not processed because LTSNR and WERKS missing
NO_DATA No B structure data exists because PI_TAB_WA empty
NO_DATA_PLANT_ALLOWED No data at plant level allowed
NO_DATA_VENDOR_SUBRANGE_ALL No data at sub-range level allowed
NO_LFA1_RELE_EKORG_MISSING Maintenance of relevance of data retention level only with purchasing org
NO_MAP No folder data exists (first record not type 0)
NO_TYPE_2 Data record is not of type 2
TABLE_NAME_MISSING Type 2 data record does not contain a table name
TABLE_UNKNOWN Table unknown in connection with TA
TAXGR_NOT_FOUND
TA_CODE_MISSING BLF00 record does not contain a transaction code
TA_NOT_ALLOWED TA does not correspond to the permissible in the table
TA_NOT_FOUND Transaction not found in table T020
TCODE_NOT_IN_T078K Transaction code not found in table T078K

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