×

[PR]この広告は3ヶ月以上更新がないため表示されています。
ホームページを更新後24時間以内に表示されなくなります。




Sapass

 Simplify SAP R/3 development with Excel VBA/VB RFC  
Home> Bapi>RepManConfirmation



Index

RepManConfirmation

RepManConfirmation


The business object REM backflush is a message about the production
situation in repetitive manufacturing. It has no reference to the long-lasting orders.


In a REM backflush, you can backflush the produced quantities and the
activities used in the production of these quantities. The components used are backflushed.


11-Dec-2005


Methods

Available Methods


  • Cancel : Reverse REM Backflush [ BAPI_REPMANCONF_CANCEL ] (Obsolete in 46C)
  • CreateMTO : Execute Backflush in Sales Order Scenario [ BAPI_REPMANCONF_CREATE_MTO ] (Obsolete in 46C)
  • CreateMTP : Execute Backflush in Production Lot Scenario [ BAPI_REPMANCONF_CREATE_PLOT ] (Obsolete in 46C)
  • CreateMTS : Execute Backflush in Stock Scenario [ BAPI_REPMANCONF_CREATE_MTS ] (Obsolete in 46C)
  • ExistenceCheck : Check Existence of Object [ BAPI_REPMANCONF_EXIST_CHK ] (Obsolete in 46C)

11-Dec-2005


Cancel

Cancel


The system reverses the PDC backflush number transferred using theparameter PLANTDATACOLLNR. This means that all documents in the R/3 system created with this PDC number are reversed. This includesmaterial documents, activity documents, reporting point documents and postprocessing documents.


If the reversal of the PDC number is not carried out successfully, thesystem issues an appropriate message via the exporting parameter RETURN. If the backflush is reversed successfully, the exportingparameter RETURN is filled with initial values.

In this module, no COMMIT WORK is executed.


Note that after accessing this BAPI, a COMMIT WORK is directly transmitted. That is, it is not possible to use several recordingbackflush BAPIs in sequence and then only transmit one single COMMITWORK after the last BAPI. If this should happen, however, the second BAPI will terminate as no such accessing chain is technically
supported.


11-Dec-2005


CreateMTO

CreateMTO


A backflush is carried out for the make-to-order scenario. If thebackflush is not successful an appropriate message is returned via the exporting parameter RETURN. If the backflush was carried outsuccessfully, the exporting parameter RETURN is filled with initial values.


The backflush is carried out for a sales order. Depending on the stockcategory (valuated or nonvaluated), the costs are collected at a product cost collector or the sales order.

Meaning of the parameters:

BFLUSHFLAGS: Controls the type and the scope of a backflush


BFLUSHDATAGEN: Parameter for the scenario-independent backflush data

BFLUSHDATAMTO: Parameter for the make-to-order scenario

SERIALNR: List of serial numbers

RETURN: Return of an error code if the backflush could not be carried out successfully.


In this module, no COMMIT WORK is executed.

Note that after accessing this BAPI, a COMMIT WORK is directly transmitted. That is, it is not possible to use several recordingbackflush BAPIs in sequence and then only transmit one single COMMITWORK after the last BAPI. If this should happen, however, the second BAPI will terminate as no such accessing chain is technically
supported.

Notes

A sales order and/or a planned order must be transferred. A PDC backflush number also has to be transferred.

The entry of a posting date and a document date is also mandatory.

If in the corresponding repetitive manufacturing profile, you have set
that a correction in dialog is mandatory in the occurrence of withdrawal errors and if a withdrawal error does exist in thebackflush, then the backflush cannot be carried out and the system displays an appropriate error code in the RETURN parameter.

If in the corresponding repetitive manufacturing profile, you have set
that a correction in dialog is optional in the occurrence of withdrawalerrors and if a withdrawal error does exist in the backflush, thesystem creates postprocessing records for the components which cannotbe withdrawn. Therefore, make sure that the creation of postprocessing
records is allowed in the repetitive manufacturing profile. Otherwise,the withdrawal errors are not logged and it is not possible to use the system-supported automatic subsequent posting option.


11-Dec-2005


CreateMTP

CreateMTP


A backflush is being executed for the production by lot scenario. Ifthe backflush is not completed successfully, an appropriate message istransferred via the exporting parameter RETURN. If the backflush iscompleted successfully, the exporting parameter RETURN is filled with initial values.


The backflush is carried out for a production lot. The costs are collected at the production lot.

Meaning of the parameters:

  • BFLUSHFLAGS: Control of the type and scope of the backflush.
  • BFLUSHDATAGEN: Parameter for the backflush data independent of the scenario.

  • BFLUSHDATAMTP: Parameter specifically for the production lot scenario.
  • SERIALNR: List of serial numbers.
  • RETURN: Return of an error code if the backflush could not be compelted successfully.
  • In this module, no COMMIT WORK is executed.

  • Notes

    Note that a COMMIT WORK is initiated directly after accessing thisBAPI. This means that it is not possible to use several recordingbackflush BAPIs in sequence and then initiate one single COMMIT WORKafter the last BAPI. Should this happen, the second BAPI will be terminated as the program does not support accessing the BAPI in
    sequence.

    A production lot and a plant must be transferred. A PDC backflush number must also be transferred.
    The entry of a posting date and a document date is also mandatory.

    If, in the repetitive manufacuturing profile, you have defined that a
    correction in dialog is mandatory should withdrawal errors occur andshould an error actually occur in the backflush, the backflush cannotbe carried out and an appropriate error code is displayed in the RETURN parameter.

    If, in the repetitive manufacuturing profile, you have defined that a
    correction in dialog is optional should withdrawal errors occur andshould an error actually occur in the backflush, postprocessing recordsare created for the components that cannot be withdrawn. Make sure thatthe creation of postprocessing records is allowed in the repetitive
    manufacturing profile. Otherwise, the withdrawal errors are not loggedand there is no way of reposting them automatically in the system.


    11-Dec-2005


    CreateMTS

    CreateMTS


    A backflush is carried out for the make-to-stock scenario. If thebackflush is not completed successfully, an appropriate message istransmitted via the exporting parameter RETURN. If the backflush wascarried out successfully, the exporting parameter RETURN is filled with initial values.


    The backflush is carried out for a material. The costs are assigned to a product cost collector.

    Meaning of the parameters:

  • BFLUSHFLAGS: Control of the type and scope of the a backflush.
  • BFLUSHDATAGEN: Parameter of the backflush data independent of the scenario.

  • BFLUSHDATAMTS: Parameter sepcifically for the make-to-stock scenario.
  • SERIALNR: List of serial numbers.
  • RETURN: Return of an error code when the backflush could not carried out successfully.
  • In this module, no COMMIT WORK is executed.


    Notes

    Note that a COMMIT WORK is initiated directly after accessing thisBAPI. This means that it is not possible to use several recordingbackflush BAPIs in sequence and then initiate one single COMMIT WORKafter the last BAPI. Should this happen, the second BAPI will be terminated as the program does not support accessing the BAPI in
    sequence.

    A material and a plant or a planned order must be transferred. A PDC backflush number must also be transferred.
    The entry of a posting date and a document date is also mandatory.

    If, in the repetitive manufacuturing profile, you have defined that a
    correction in dialog is mandatory should withdrawal errors occur andshould an error actually occur in the backflush, the backflush cannotbe carried out and an appropriate error code is displayed in the RETURN parameter.

    If, in the repetitive manufacuturing profile, you have defined that a
    correction in dialog is optional should withdrawal errors occur andshould an error actually occur in the backflush, postprocessing recordsare created for the components that cannot be withdrawn. Make sure thatthe creation of postprocessing records is allowed in the repetitive
    manufacturing profile. Otherwise, the withdrawal errors are not loggedand there is no way of reposting them automatically in the system.


    11-Dec-2005


    ExistenceCheck

    ExistenceCheck


    A check is peformed for the PDC backflush number transferred with theparameter PLANTDATACOLLNR to see whether a backflush has already beencarried out using this number. This number is not the internallyassigned number from the R/3 system. It is assigned by the PDC system.


    If the check of the PDC backflush number is not successful, an appropriate message is issued via the exporting parameter RETURN.Otherwise, the parameter RETURN is filled with initial values.

    In this module, no COMMIT WORK is executed.


    11-Dec-2005