Composant : Logistics Information System -

Solution : https://service.sap.com/sap/support/notes/99507 (Connexion à SAP Service Marketplace requise)

Résumé :
This SAP Note addresses terminations in update programs following an upgrade, client copy, or transport, specifically in customer-specific update programs within RMCX namespaces. Symptoms include ABAP runtime errors such as 'PERFORM_TOO_MANY_PARAMETERS', among others. Misalignments in TMC2* control tables or outdated update programs are identified as causes. The solution involves referencing related notes for consistency checks and regeneration instructions. For updates on custom structures from S500 to S999, procedures using MC25 or RMCSISGN are outlined. Important to avoid updates during program generation to prevent inconsistencies, and deletion of ZLISDEL post-generation is crucial.

Mots Clés :
customer-specific updating definitions, customer-defined updating definitions, runtime error syntax_error occurs, customer-specific update groups, abap/4 runtime error occurs, customer-specific update programs, syntax error reason, customer namespace s500, routine f00 _update, incorrect updates occur

Notes associées :

1319517	Unicode Collection Note
1002904	Analysis of TMC2P, TMC2Q and TMC2F
778122	Upgrading to SAP ECC 5.0 with SAP ECC AFS 5.0
651373	LIS: Update parameter cannot be changed
534826	LIS: Current update programs after upgrade
310520	Error messages in XPRA RMCSXP03 or RMCSCLCC
309335	Update terminations in LIS
217178	CS 4.5B: Additions to the upgrade guide
204130	SIS update: Collective note
198960	Copies from client: Incorrect update rules
196241	Termination for XPRA RMCSXP03 Release 4.x
188083	Update terminations after client copy (remote copy)
183654	Missing update simulation/log and new setup
179204	LIS: Error in method execution after transport
136303	SIS: Termination 'PERFORM_NOT_FOUND' in program RMCX****
119101	Generation of SAP information structures possible
96165	Trmnation during upgrade to 4.0A/B in XPRA RMCSXP03