SAP Program RCSBI010 - Create BOMs using Batch Input

Description
This report is used to copy bills of material without a longtext from an external system to the SAP System. It supports thecreation of document structures, equipment BOMs, material BOMs,standard object BOMs, and functional location BOMs.
The program reads the sequential file entered and processes the data init.

  • The sequential file can be on your local application server, the
  • presentation server, or an external application server. In the lattercase, you must enter the server name.
    • If you want the system to write the data to one or more batch input
    • sessions, which you can process manually later, select the reportparameter "Create session".
      If you leave the report parameter "create session" with its initialvalue, all the bills of material are created online. In this case, onlythose BOMs where an error occured when they were created are collectedin batch input sessions. You can then edit these later.

      Precondition
      Before you can start this report, you need to extract the BOM data tobe copied from the source system and write it to a sequentialfile. To do this, you need to implement a program in the source systemthat compiles the data in the prescribed format and creates the file.
      You must define a logical name for the sequential file in thecustomizing functions. This logical name is the reference to thephysical name. You can maintain the logical name when you start thereport, by calling online help (F1) on the Logicalfile name field.
      The format for the BOM data in the sequential file is as follows:

      • Record type 0: one session record (structure BGR00) per session

      • The session header contains general administrative data on the batchinput session to be created. All records that follow the header in thesequential file are assigned to the current session, until the nextheader occurs in the file.
        • Record type 1: one session record (structure BICSK) for each BOM

        • The BOM header record contains the transaction code (for example, CS01Create material BOM) and the header data.
          In the field BICSK-TCODE in structure BISCK, you define the BOMcategory. The BOM category determines the SAP transaction to be called.The following entries are possible:
          - CV11 for document structures
          - IB01 for equipment BOMs
          - CS01 for material BOMs
          - CS51 for standard BOMs
          - IB11 for functional location BOMs
          • Record type 2: one item record (structure BICSP) per item

          • All BOM item records are assigned to the preceding BOM header, untilthe next BOM header or session header occurs in the sequential file.
            • Record type 3: one sub-item record (structure BICSU) per
            • sub-item
              All BOM sub-item records are assigned to the preceding BOM item, untilthe next item header, BOM header, or session header occurs in thesequential file.

              Note
              Please note the following points when you create the sequential file:

              • Fields where no entry is to be made should be copied with their initial
              • value. Do not use any NODATA character defined in theBGR00-NODATA field.
                • If you want to remove a default field entry for the transaction, enter
                • the delete character "!" in the field concerned. For example, if youwant to set the "bulk material" indicator, and the "relevancy tocosting" indicator is a default setting for the transaction, you needto remove the "relevancy to costing" indicator.
                  • Fields that contain a date should be copied in the external format
                  • defined in the user master record. One exception is the date entered inthe session header, if any. This should always be copied in internalformat YYYYMMDD, such that YYYY is the year, MM is the month and DD isthe day.
                    • If fields for quantities or prices contain decimal values, always use
                    • the decimal point defined in the user master record.

                      Procedure
                      RESET N1
                      Extract the data to be copied from the source system using the programwritten for this purpose, writing the data to a sequential file.
                      Start the transfer program in the SAP System.
                      Enter the logical file name of the physical path containing thesequential file.
                      To find the path name, you can select the possible entries function.
                      Decide from which server you want to import the sequential file. Youcan choose either your local application server, an externalapplication server, or the presentation server.
                      If you choose an external application server, you need to enter itsname. You can use the possible entries button to help you.
                      Decide whether you want to create sessions for all imported BOMs oronly those that contain errors.
                      The result log for data transfer tells you which sessions, if any, havebeen created.
                      Process the sessions, in order to copy the bills of material to thesystem, or in order to edit the bills of material containing errors.

                      Output
                      Once the data program has run, you see a log with the followinginformation:

                      • all the errors that occured during processing

                      • all the BOMs that were copied successfully

                      • all the sessions, if any, that have been created

988662Error 00 261 during AFS BOM batch input
931562Categories not created for AFS BOM items via batch input
720598LSMW calls BOMs batch input with NODATA = '/'
545676FAQ BOM data transfer
502476Categories in BOMs are not saved
501564Create BOM via batch input, lowercase letter
208776Batch Input:Customer flds mssng f.variable-sze itms