SAP Function BAPI_PROCORDCONF_CREATE_TT - Enter Confirmation Time Ticket for Process Order

Parameter Reference Type Length Default Optional Text
POST_WRONG_ENTRIES BAPI_CORU_PARAM-INS_ERR C 1 '0' X Key: Insert incorrect confirmation
TESTRUN BAPI_CORU_PARAM-TESTRUN C 1 X Switch to Simulation Session for Write BAPIs

Parameter Reference Type Length Text
RETURN BAPIRET1 u 470 Return Parameters

Parameter Reference Length Optional Text
DETAIL_RETURN BAPI_CORU_RETURN 568 X Return Information for APIs
GOODSMOVEMENTS BAPI2017_GM_ITEM_CREATE 1106 X BAPI Communication Structure: Create Material Document Item
LINK_CONF_CHAR_WIPBATCH BAPI_LINK_CONF_CHAR_WIPBATCH 8 X Linkage of Confirmation with Characteristics WIP Batch
LINK_CONF_GOODSMOV BAPI_LINK_CONF_GOODSMOV 12 X Link: Confirmation with goods movements
TIMETICKETS BAPI_PI_TIMETICKET1 537 BAPI Structure: PP Confirmation Time Ticket

You can use this method to enter time tickets for phases ofprocess orders.
In addition, goods movements that should be posted with a confirmationcan also be transferred.
If no goods movements are specified for a confirmation, they aredetermined in accordance with the standard logic for backflushes andautomatic goods receipt for the confirmation.
Creation of a WIP Batch
During the entry of a confirmation, you can additionally create a WIPbatch. This functionality is available as of Enhancement Package 4 forERP2005. To be able to use the functionality, you must activate theBusiness Function LOG_PP_WIP_BATCH. In addition, you must activate theWIP batch in Customizing under Logistics General -> Batch Management-> WIP Batches -> Activate WIP Batch aktivieren.
To create a WIP batch with a confirmation, you must specify a batchnumber in the WIP_BATCH field of the table TIMETICKETS. The WIP batchspecified must not yet exist - it is created when the confirmation isposted.
If internal number assignment is to be used for the batches, you mustenter the * sign (asterisk) in the WIP_BATCH field instead of a batchnumber.
Authorization check

The PostWrongEntries parameter controls which confirmations aretransferred into the error pool.
You can correct and re-post the error pool entries via thepost-processing of confirmations.

Value range

  • 0: No confirmations

  • 1: Only incorrect confirmations

  • 2: Incorrect confirmations and confirmations that cannot be processed
  • due to a lock situation.

    0: No confirmations.

    The Testrun parameter controls whether the confirmation data isdesignated for posting or should just be checked in the test mode.

    Value range

    • X: The confirmation data is checked in the test mode.

    • No objects are locked against access.
      • Blank: The confirmation data is intended for posting after it has been
      • successfully checked.
        Lock entries are set for the affected objects.

        Blank: Test mode

        Table of the characteristics of a WIP batch that is to be created.
        Enter the characteristic name in the CHAR_NAME field and theassociated characteristic value in the CHAR_VALUE field.
        The characteristic name that is passed on must be defined in the classof the material that is to be classified. You must specify the technicalname of the characteristic, not the short description.
        If a characteristic name that is passed on is not defined in the classof the material, the system ignores the table entry. No error message isissued.
        If a mandatory characteristic is not valuated, the WIP batch is creatednevertheless. In this case, the classification of the WIP batch acquiresthe status Incomplete.

        The DetailReturn table provides one of the following pieces ofinformation for each confirmation:

        • Successful posting

        • Exception situation (because of incorrect data or current lock
        • situations)
          For each confirmation transferred in the Timetickets table, anentry is made in the DetailReturn table.
          For the successful posting of a confirmation, the key of theconfirmation is made available in the CONF_NO andCONF_CNT fields.
          Otherwise, all the details for the exception situation are madeavailable in the respective fields and the report text is transferred inthe MESSAGE field. In the event of a lock situation, theFLG_LOCKED

          The Goodsmovements table contains goods movements that should beposted with reference to the confirmations.
          The following automatic goods movements should be posted together withconfirmations:

          • Backflushes of components

          • Automatic goods receipts for the assembly

          • To complete or correct the goods movements, the data can be transferredto the Goodsmovements table.
            Goods movements are assigned to the respective confirmation via theLinkConfGoodsmov table.
            If at least one goods movement is assigned to a confirmation, then noautomatic goods movements are determined on saving.


            When posting goods movements via the confirmation, you cannot use theentire MM functionality. This applies to the confirmation dialogtransactions and also to the confirmation BAPIs.
            The indicator NO_TRANSFER_REQ= X in the goods movements table isset to prevent the generation of a transport requirement when the goodsmovement is executed. The inventory stock management structureBAPI2017_GM_ITEM_CREATE is used to transfer goods movements toconfirmation BAPIs. However, this contains some fields that do not playa part in or are not supported for confirmations for production orders.Therefore, the indicator has no effect.

            The assignment of each individual characteristic valuation to a WIPbatch is carried out via the parameter table LinkConfCharWIPBatch
            . Characteristic valuations that are not assigned to a WIP batch arenot taken into account.
            The assignment is effected via the indexes IndexConfirm andIndexCharWIPBatch. The index IndexConfirm must referencethe entry in the parameter table Timetickets and the indexIndexCharWIPBatch the entry in the parameter tableCharacteristicsWIPBatch.
            This means that, as a rule, the number of entries in the tableLinkConfCharWIPBatch corresponds to the number in the tableCharacteristicsWIPBatch.

            The LinkConfGoodsmov table assigns each goods movement item to aconfirmation.
            The assignment is made via the indexes IndexConfirm andIndexGoodsmov:

            • IndexConfirm refers to the entry in the AtHdrLevels table

            • IndexGoodsmov refers to the entry in the Goodsmovements
            • table
              Items that are not assigned to any confirmation are not taken intoconsideration on saving.
              If you want to prevent goods movements from being automaticallydetermined for a confirmation, because none have occurred, then you cando this via an entry in the LinkConfGoodsmov table, withoutmaking an entry in the Goodsmovements table.
              In this case, the IndexConfirm field must refer to the affectedconfirmation and the IndexGoodsmov field must have the initialvalue 0.

              The Timetickets table transfers confirmations as time tickets.
              The confirmed object phase can be identified in one of the followingways:

              • By the confirmation number in the CONF_NO field

              • By a combination of the following entries:

              • Order in the ORDERID field
                Phase in the PHASE field
                Possible secondary resources in the SEC_RESOURCE field
                Each entry in the Timetickets table represents a separateconfirmation that is processed in the sequence transferred.