|
Functionality
Using this method you can enter confirmations for network activities/activity elements and splits.
Goods movements for a confirmation are specified according to thestandard logic for retrograde withdrawal and automatic goods receipt forconfirmation. Notes
Note that directly after you call the BAPI a COMMIT WORK is carried out.This means it is not possible to use multiple write confirmation BAPIsin a row and then carry out a single COMMIT WORK only once after thelast BAPI. However, if this does occur, the system will terminate thesecond BAPI because a chain of calls, such as this, is prevented in atechnical way by the system.
If you do not carry out a COMMIT WORK, you cannot confirm a network youcreated and released using a BAPI since it does not exist in thedatabase yet. First carry out the COMMIT WORK to write the activity tothe database, and then create your confirmations. Description
The return parameter is only used for serious errors. If a seriouserror occurs, confirmations cannot be sucessfully processed. Errorsnormally only occur if transferred confirmation data cannot betransferred to internal structures, because conventions regarding datadefinitions are not held to. Value range
If no serious errors are found, the return parameter is returned withinitial values. Description
Number of the network Description
Using the Post_Wrong_Entries parameter you can control if theconfirmations to be created in exception situations (data with errors/locked objects) are still to be accepted by the SAP system and added toto the pool of confirmations with errors.
The system logs exceptions for confirmations in the E_MESSAGE_TABLEparameter table.
You have the following options with the Post_Wrong_Entries parameter:
" ": Confirmations without exceptions are posted. All otherconfirmations are rejected and not transferred to the error pool.
"1": Confirmations without exceptions are posted. All confirmationswith data errors are transferred to the error pool. Confirmations,which cannot be posted due to a lock situation, are on the other hand,not processed. This means these types of confirmations are nottransferred to the error pool.
"2": Confirmations without exceptions are posted. All confirmationswith data errors or lock situations are transferred to the error pool. Description
Indicator you use to control whether the confirmation data is intendedfor posting or if the confirmation data is only checked in the testmode. You cannot lock objects to avoid that multiple users access themin the test mode. Value range
"X": Transferred data is only tested in the test mode.
" " : The confirmation data is intended for posting after a successfulcheck. For this reason, lock entries are also carried out for theaffected objects Default
Confirmation data is intended for posting with the preassigned value,as long as no errors are found. Description
This parameter table gives information about the successful posting ofeach individual confirmation in the Time tickets table and about thedetermined exception situation based on data with errors or the currentlock situation.
An entry is added in the DetailReturn table for each confirmationtransferred to the Time tickets table. This means, for example, thatthe third entry in the DetailReturn table provides information aboutposting the third confirmation in the Time tickets table. Description
You can transfer information to multiple confirmations in the tableI_CONFIRMATIONS.
The object to be assigned is identified by network/activity andpossibly activity element.
If a confirmation results in a split, then you must specify thecapacity category and the split, in addition.
Each entry in this table contains all information for a separateconfirmation. It is checked and processed in the same order. |