You are on page 1of 5

Issue

Issue: False131 movement (Production Confirmation) entries in COGI

Impact – Nil ( 2 fictitious records appeared in COGI)

Severity – Low

Occurrence – Rare ( Over 3.5 lac, 23 such record appeared)


Issue Detail
Issue detail: Production confirmation is triggered through SCM server with
enabled serialized enhancement
Few of the entries sometimes appear in COGI even after successful production
confirmation and consumption.

Issue Analysis: Entries appear COGI though successfully posted, with no impact
on Production confirmation and consumption

Corrective Action:
• Daily monitoring and deletion of these records
• Issue highlighted to SAP
SAP OSS Status

SAP OSS Message Status: Message 648755 raised on 25th Jul’12

Current status : SAP suggested for new development


Issue reported SAP Reply
Solution Proposal

• Option 1: SAP Development to fix the bug on chargeable basis


Risk: Error may be repeated in future after correction. Current development
has been already verified during SAP safe guarding / max attention even
though error is repeating .

• Option 2 : TTL Workaround


Program ZPPBDC_IPPE_AUTOREPRO_131, is executed every 15 minutes
to clear 131 132 records this clears the correct records stuck in COGI due to
material locking (Ignoring the fictitious records) . Need to extend the program
to additionally correct the fictitious records
1) This workaround will delete the false entries appeared in COGI
2) Since deleting of COGI entries evolved risk, detail Feasibility need to be
done, before development
3) Time estimate for development will be done after feasibility
End

You might also like