Fonction SAP BAPI_PLANNEDORDER_CREATE - Create planned order

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
HEADERDATA BAPIPLAF_I1 u 262 Header data (from external system)

Paramètre Reférence Type Long. Description
CAPACITYHEADERDATA1 BAPI_KBKO u 83 Capacity header data (detailed scheduling)
CAPACITYHEADERDATA2 BAPI_KBKO u 83 Capacity header data (rate-based scheduling)
CAPACITYHEADERDATA3 BAPI_KBKO u 83 Capacity header data (rough-cut scheduling)
CREATEDHEADERDATA BAPIPLAF_E1 u 747 Header Data (from SAP for the Ext. System)
PLANNEDORDER BAPI_PLDORD-PLDORD_NUM C 10 Planned order number
RETURN BAPIRETURN1 u 470 Completion confirmations

Paramètre Reférence Long. Facultatif Description
CAPACITYDATA1 BAPI_PLDORDCAPA_E1 103 X Capacity data (detailed scheduling)
CAPACITYDATA2 BAPI_PLDORDCAPA_E1 103 X Capacity data (rate-based scheduling)
CAPACITYDATA3 BAPI_PLDORDCAPA_E1 103 X Capacity data (rough-cut scheduling)
COMPONENTSDATA BAPI_PLDORDCOMP_I1 159 X Component data - create
CREATEDCOMPONENTSDATA BAPI_PLDORDCOMP_E1 300 X Created component data

Functionality
This method can be used to create planned orders with BoM explosion orwith manual entry of components.
To help you to understand how the method can be used, test transaction"MDBA" is available. It has integrated all 6 planned order methods intoa transaction to deal with planned orders. For more information, pleaserefer to the program documentation on this transaction. The name of theprogram is 'MDBAPI01'.

Notes
The following authorization objects are checked with the activity H(Create):

  • M_PLAF_ORG

    • Transfer:
    You have to pass on the header data of the planned order together withthe component data (optional).

    Further methods:

    • PlannedOrder.ExistenceCheck

    • CommitWork

      • If you have decided that the planned orders created using this methodare to be saved to the database, you have to call up the methodCommitWork. You can find moreinformation in the parameter documentation of the parameters below.

      Confirmation:
      Messages are received back in the parameter 'Return'. You can findreturn values and their meaning in this parameter documentation.

      Description
      When a planned order has been successfully created by the method, thecapacity header data of the planned order will be exported via thisparameter if detailed scheduling data exists.
      You can find information on the meaning of individual parameter fieldsin the corresponding data element documentation in the ABAP Dictionary.

      Description
      When a planned order has been successfully created by the method, thecapacity header data of the planned order will be exported via thisparameter if rate-based scheduling data exists.
      You can find information on the meaning of individual parameter fieldsin the corresponding data element documentation in the ABAP Dictionary.

      Description
      When a planned order has been successfully created by the method, thecapacity header data of the planned order will be exported via thisparameter if rough-cut scheduling data exists.
      You can find information on the meaning of individual parameter fieldsin the corresponding data element documentation in the ABAP Dictionary.

      Description
      If the planned order was created correctly by the method, thisstructure will have the complete set of header data for the createdplanned order. You can use this data to decide whether the plannedorder should really be created.
      INCLUDE BAPI_DATAELEMENT

      Description
      You can find information on the meaning of the planned order number inthe data element documentation:
      planned order number
      INCLUDE BAPI_KEYFIELD

      Default

      Description
      INCLUDE BAPI_TABLE

      Value range

      Error messages

      Type ID Number Message
      E MD 658 Enter order type
      E MD 659 Enter a planning plant
      E 61 179 Enter a material
      E 61 212 An order quantity of 0 is notallowed
      E 61 402 No authorization for &
      E MD 130 You do not have thenecess.authorization for this function (see long text)

      Informative messages

      Type ID Number Message
      E 61 768 The system could not determinea storage location
      I 61 027 No material components weredetermined

      Success messages

      Type ID Number Message
      S 61 010 Planned order & created

      Description
      This is an important parameter in form of a structure. The parametersin this structure are parameters that can be changed using this method.You can find information on the meaning of individual parameter fieldsin the corresponding data element documentation in the ABAP Dictionary.

      Description
      When a planned order has been successfully created by the method, thecapacity data of the planned order will be exported via this parameterif detailed scheduling data exists.
      You can find information on the meaning of individual parameter fieldsin the corresponding data element documentation in the ABAP Dictionary.

      Description
      When a planned order has been successfully created by the method, thecapacity data of the planned order will be exported via this parameterif rate-based scheduling data exists.
      You can find information on the meaning of individual parameter fieldsin the corresponding data element documentation in the ABAP Dictionary.

      Description
      When a planned order has been successfully created by the method, thecapacity data of the planned order will be exported via this parameterif rough-cut scheduling data exists.
      You can find information on the meaning of individual parameter fieldsin the corresponding data element documentation in the ABAP Dictionary.

      Description
      You can create components manually for the planned order, in that youenter the necessary data for this as a parameter in this table.
      INCLUDE BAPI_DATAELEMENT

      Description
      If a planned order has been successfully created by the method and hasmaterial components, all material components data will be exported withthis parameter.
      You can find information on the meaning of individual parameter fieldsin the corresponding data element documentation in the ABAP Dictionary.

1478012Error 8J 843 during AFS planned order create/change via BAPI
1486675Error 8J 843 in BAPI_PLANNEDORDER_CREATE for AFS materials
1466837Error 82 807 during plnd ord. creation for AFS matl via BAPI
1471616Incorrect SKU / markers created via BAPI_PLANNEDORDER_CREATE
1075141BAPIs valid for usage with AFS6.0
1131899Order & scrap quantity set to 0 via BAPI_PLANNEDORDER_CHANGE
1101029Issues with AFS BAPI for planned order create and change