Fonction SAP BAPI_PRODORDCONF_CREATE_ACT - Enter activity confirmation

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
POST_WRONG_ENTRIES BAPI_CORU_PARAM-INS_ERR C 1 '0' X Ind.: Incorrect Data in Error Pool

Paramètre Reférence Type Long. Description
RETURN BAPIRET1 u 470 Return Parameter

Paramètre Reférence Long. Facultatif Description
ACTIVITIES BAPI_CORU_ACTIV 271 Table of Activity Confirmations
DETAIL_RETURN BAPI_CORU_RETURN 568 X Return Parameter for Confirmation Table

Functionality
You use this method to enter pure activity confirmations foroperations in production orders.
Activity confirmations are special, since they do not generally afffectthe confirmation status. Only if the very first confirmation for anoperation is an activity confirmation, does the operation receive thestatus "partially confirmed".

Notes
INCLUDE BAPI_PRODORDCONF_HINT_COMMIT OBJECT DOKU ID TX
Authorization check
The authorization object C_AFRU_AWK is checkedtogether with the activity 01 (create) as well as the order type andplant of the production order to be confirmed.
Parameter

  • PostWrongEntries

  • You use the PostWrongEntries parameter to control whether in anexception (incorrect data/ locked objects) the confirmations areaccepted by the SAP system and placed in the pool of incorrectconfirmations.
    Exceptions for confirmations are logged in the DetailReturnparameter table.
    The following characteristic values of the PostWrongEntriesparameter are possible:
    " ": Confirmations, in which no exception occurred, are posted. All theconfirmations are not processed, they are not placed in the pool forincorrect confirmations.
    "1": Confirmations, in which no exception occurred, are posted. Allconfirmations with incorrect data are placed in the pool for incorrectconfirmations. On the other hand, confirmations that are not posted duea lock situation are not processed, they are not placed in the pool.
    "2": Confirmations, in which no exception occurred, are posted. Allconfirmations with exceptions are placed in the pool.
    • Return

    • If confirmations could not be processed, due to a serious error, youreceive information about the error in the Return parameter.
      • Activities

      • The data from the activity confirmation is copied to the Activities
        table.
        • DetailReturn

        • The DetailReturn table informs you for each confirmation to beentered, whether a confirmation could not be entered due to a lockconflict or which error occurred.
          If the confirmation could be enterd successfully, the key of theconfirmation is logged in the fields DetailReturn-Conf_No andDetailReturn-Conf_Cnt.
          In the case of a lock conflict, the DetailReturn-Flg_Locked indicator is set.
          If the data is found to be incorrect, a corresponding error message iswritten in the relevant fileds of the DetailReturn table.

          Description
          The Return parameter is only used for serious errors that prevent allconfirmations from being processed further. As a rule, this type oferror only occurs if the transferred confirmation data cannot beconverted into the internal structures, because conventions regardingdata definitions have not been adhered to.
          The Return parameter's structure contains all the necessaryinformation about the error in detail. This is also prepared in themessage text MESSAGE.

          Default
          If no serious error is found, the return parameter is returned withinitial values.

          Description
          Controls which confirmations are transferred to the error pool.
          Error pool entries can be corrected and posted usingReprocessing Confirmations.

          Value range

          • 0: Neither confirmations with errors nor confirmations that cannot be
          • processed due to a lock situation are transferred to the error pool.
            • 1: Confirmations with errors are transferred to the error pool, whereas
            • confirmations that cannot be processed due to a lock situation are nottransferred to the error pool.
              • 2: Both confirmations with errors and confirmations that cannot be
              • processed due to a lock situation are transferred to the error pool.

                Default
                The default value is "0". That is, no confirmations are transferred tothe error pool.

                Description
                Table of confirmations to be entered, as activity confirmations.
                You can identify the confirmed operation by entering theconfirmation number in the CONF_NO field. Alternatively, you canidentify the operation by entering the order, sequence and operation,and if necessary the sub-operation, in the ORDERID,SEQUENCE, OPERATION and SUB_OPER fields.
                If an individual capacity is being confirmed, you can identify theindividual capacity with the help of the CAPA_CATEGORY andSPLIT fields, as well as entering the operation.
                Each entry in the Activities table represents a separateconfirmation that is checked and processed in the sequence in which itis transferred.

                Description
                The parameter table DetailReturn provides information about thesuccessful entry of each individual confirmation in theActivities table, or about any exceptions that occur due toincorrect data or a current lock situation.
                An entry is made in the DetailReturn table for each confirmationthat is transferred to the Activities table. For example, thethird entry in the DetailReturn table provides information aboutthe posting of the third activity confirmation in the Activitiestable.
                If an activity confirmation is successfully entered, the key assignedto the confirmation is found in fields CONF_NO andCONF_CNT. Otherwise, all details about the exception are foundin the individual fields, but also transferred in the prepared messagetext MESSAGE. If a lock situation occurs, the FLG_LOCKEDindicator is also set.

744403Confirmation BAPI's do not produce any results