sachins.murab

Challenges in Central contract Distribution Process:-

During distribution of Central contract it might be possible that some line items (Materials) are not maintained in respective backend systems .For example it might possible that Material not maintained Respected Plant/Deleted from plant etc .These status of Products not updated to SRM system .

From buyer perspective central contract distribution stuck due to Master data issue .In these cases currently following steps need to be performed for successful distribution of central contract :-

Get the updates from buyer that Central contract fail to replicate in backed system OR
Perform Monitoring for erroneous documents
Maintained/Update Master data .I.e. Extend material in respective plants.
Discard/After confirmation of data maintenance Reprocess the message from Forward Error Handling (FEH)

Inform the Buyer to redistribute the Central contract.

This is two way activity where buyer have to wait until he received Master Data update and than redistribute respective central contract .Upon successful distribution Outline Agreement created based upon configuration.

Solution Approach to overcome Data dependency

We should use “Error and Conflict Handler” in system landscape to get the actual update for distributed document which flows through from Process Integration (PI).In case Business Document i.e. Central contract stuck in FEH of backend system due to some Master data issues can be notified to document processing person or business user.

We can use BAPI call/custom development which will be call from portal where Material Extend/Update can be maintained by contract processing officer.

Contract officers can access these iViews (to call BAPI/custom FM) .Master data i.e. Material can be process in backed using following ways:-

Using BAPIs Material can be extend/update in plants
Custom Function Module
BDC call in backend system

On successful completion of Master data creation we can Re-Process FEH Message or Discard FEH Message and contract officer will re-distribute the central contract.

Pre-requisite

Activate Forward Error Handling (FEH)

Customer has to maintain the followed table: /n/SAPPO/LOGSYS, where he should assign the logical system to

software component (ex CA-SOA-ESM-SRM-PUR) as shown below :-

FEH needs to be activated to capture the error messages using Cross-Application Components -> Processes

and Tools for Enterprise Applications Enterprise Services -> Error and Conflict Handler ->

Activate Error and Conflict Handler.

Error and Conflict Handler

The Error and Conflict Handler requires the use of the Post-processing Office component

Reference:

SAP Note: - 1270081

SRM-PLM Organisation Structure Re-Structuring via Dis-Integration of HR System

Integrated SAP HR and SRM and PLM system creates lot of junk data which is not required in SRM/ PLM organisation structure .Due to HR replication any changes in existing position generate IDoc which cause inconsistency in existing user’s position assigned to organisation structure.

After Disintegration of SAP HR system; user assignment into SRM organisation structure solely carried out in SRM system .Replication issues like incomplete data, Business Partner incompleteness will no longer exist .System performance will increased and data exchange and monitoring activity reduced at larger extent .

Scope & Version: SRM & PLM Organisation Re-Structuring with SRM 4.0

SAP HR Dis-Integration can be achieved with following setting in configuration table T77S0 with the help of SM30 transaction.

Group | Sem. Abbr | Value abbr.| Description

_______________________________________________________________________

HRALX | HRAC | X | Activate HR Integration

HRALX | OADBP | Optional | Business Partner of Standard Address

HRALX | OADRE | | Address necessary for Bus. Partner?

HRALX | OBPON | ON | Integration O-BP activated

HRALX | PBPHR | OFF | Integration Employee/BP Activate

During Organisation restructuring we have faced following issues and found their solutions :-

1. Consistent user become Inconsistent after reassignment .

We need to be executed report B_REPAIR_EBP_USER_2 with level 1 (No New BP generated) .

2. Workflow linkage warning Message crop up.

This warning message rose after a call of H_GET_LEADING_POSITION during user check (BBPU_CHECK_EBP_USER)/check with USERS_GEN.

Resolution: In workflow configuration (table T77S0) you can set the indicator WFLOW/CRMUS to 'X'.

3. Restriction of Product Category in organisation structure .This is standard SRM issue in all releases.

If we restrict Product categories in "Extended Attributes" of organisation structure only works for search help restriction. If user maintained restricted product category directly at Item level it won’t give any error message. It’s bug in all the SRM release .We are in discussion with SAP for this.

For PLM system, after HR disintegration following activities need to be performed to assign SU01 user to PLM organisation structure:

1. Create Employee Business Partner from BUM1 transaction.

2. Create Central Person(CP) with BP transaction.

3. Create Position with the help of PPOME .

4. Staff user into organisation structure to designated organisation unit .

5. Assign Central Person, user to the position using "Staffing Management" .

Reference

SAP Notes:

797879 - EBP 4.0+: Setting up business partner integration

550055 - EBP/CRM: New integration for business partner

1024258 - HRALX: PPOME Drag&Drop: BP-BP relationships not deleted

SAP Forums