Paramètre | Reférence | Type | Long. | Valeur par déf. | Facultatif | Description |
---|---|---|---|---|---|---|
I_PROJECT_DEFINITION | BAPI_BUS2001_NEW-PROJECT_DEFINITION | C | 24 | Project Definition |
Paramètre | Reférence | Long. | Facultatif | Description |
---|---|---|---|---|
ET_RETURN | BAPIRET2 | 548 | X | Return Parameter |
EXTENSIONIN | BAPIPAREX | 990 | X | Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT |
EXTENSIONOUT | BAPIPAREX | 990 | X | Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT |
Functionality
If all checks are successful, the project definition is deleted in thedocument tables. If the project has WBS elements, these are also deleted. If the projecthas other objects such as networks, activities and so on, the BAPIterminates and an error message is displayed. These must be deletedbeforehand. The BAPI does not delete these automatically. The project definition is deleted as soon as a LUW (Logical Unit ofWork) has been completed with the BAPI BAPI_PS_PRECOMMIT and COMMITWORK. Only one project or one WBS element from a project can be processed ata time in one LUW. You cannot delete temporary objects. This means that if you create aproject in an LUW, you cannot delete it immediately after creating it.You can delete it using this BAPI only after you physically create theproject using the BAPIs "BAPI_PS_PRECOMMIT" and "COMMIT WORK". The return parameter "RETURN" displays first an error or successmessage for all objects (project definition and if relevant, associatedWBS elements) that states whether the project definition or theindividual WBS elements could be deleted. The first message variable isthe object category, the second is the object ID and the GUID (if itwas possible to read it) is in the fourth message variable. Allmessages that were generated during the processing are listedunderneath, and the parameters of the individual messages are filledwith the object ID. Notes Further information Description |