Synchronization between Contract and Project.docx

7/29/2019 Synchronization between Contract and Project.docx

http://slidepdf.com/reader/full/synchronization-between-contract-and-projectdocx 1/23

Synchronization between Contract and Project

Abstract:

SD Contracts and Project WBS Elements are independent objects in ECC that are linked via a WBS

Element reference (PRPS-PSPNR) number. In native SAP, the WBS Element status can change withoutany intelligent reference to SD Contract statuses. This status change at WBS Element (Level 2) levelneeds to be controlled and synced up to Contract status (and vice versa) so that status integrity for Contract and Project WBS Elements is maintained.

Also most of the Project Systems master data elements will be automatically populated and synchronizedbased on attributes in related SD Contract line items.

Description

For professional based projects, a Project / WBS Element structure is linked to a SD Contract. SDContract document and WBS Element have system statuses that define the tasks that can be done onthese documents. Some of these statuses have to be kept in synch to keep the process integrity of the

SD Contract and WBS Elements. For example, an SD Contract document can not be closed, if the WBSis still in „Released‟ status. Native SAP does not provide a control of status from SD Contract to WBS andvice-versa

Native Project System does not have the functionality to maintain / sync-up SD Contract and WBSElement statuses and field attributes. This has been identified also as GAP (refer GAP_OTC_PR-076) and would require development effort to meet the above requirements.

If the above enhancement is not developed, then the contract and WBS statuses and field informationcan get out of sync, causing a loss of data capture integrity. For example, if contract is completely closed,but WBS Element status allows cost capture for that contract, can cause costs not reported for thecontract. Also change of Project Manager / Engagement Manager Information from SD Contracts not insynch with Person Responsible information on Project / WBS Elements.

The synchronization of System and User Statuses between SD Contract Line Items and Project WBSElements for Custom Contracts will span from “REL (i.e. Released)” to “FNBL (Final Billing)” status of SDContract Line Items. The setting of system status to “TECO (Technically Completed)” or “CLSD (Closed)”will be carried out by either another program or manually done by end user. The synchronization of fieldinformation between SD Contract Line Items and Project WBS Elements will be continued till WBSElement has “CLSD (Closed)” system status.

The synchronization process will update field and system & user status information on Project Definition,WBS Element Level 1 and WBS Element Level 2. For WBS Elements Level 3 and below, the status andother information will be manually updated by Project Managers. During the synchronization process, theinformation will flow from SD Contract / Contract Line Items to Project Definition / WBS Elements. Thereverse scenario is not applicable.

There are two parts in this development, 1st part comprising the synchronization of data betweenContract and the level2 WBS that has been attached.

Please click here for the sample code.

Data Synchronization between the Contract and Project :

http://sapfunctional.com/PS/Sync/Code.htm






The Following BAPI BAPI_PROJECT_MAINTAIN is very useful for synchronizing the data between theProject and the Level2 WBS Element.

The Following Example Demonstrates How Data Synchronization Takes place between Contract andProject:

The Below Screen Shot Shows the Contract Line Item Details:

The Level2 WBS Attached to it is C.00965.001.002 and The Start and End dated of the Line Item are06/29/ 2010 and 07/05/2010

The Following Screen Shot Shows The responsible that has been given at the Contract Line Item:

The Employee responsible given is 106(Peck Troy) which needs to be Synchronized with the WBSattached



The Status of the Level2 WBS before Synchronization is

See below, there are No dates Before Synchronization:



The Following are the results after Synchronization Process:



The Second part of our development Includes Status Synchronization:

There are 3 cases in this Case:

Case1: High Volume Low Value (HVLV) Contracts / Project







According to Z table The Following Synchronization has to take place :



After Synchronization the Following changes has to occur:

Data has to be synchronized and Person Responsible has to be Synchronized and also dates and Statusas well

Results after Synchronization Process:



Scenario 2: Custom Contracts with One Contract Line Item mapped to One WBS Element













The Results after Synchronization:







Scenario 3: Custom Contracts with Multiple Contract Line Items mapped to One WBS Element









Documents

Synchronization between Contract and Project.docx