PACG 110 / S4PACG 100 SP3 SAP NOTES
- proaxia
- proaxia
If not stated otherwise all notes can be applied to both component versions of FSM Connector PACG 110 and S4PACG 100
Service Orders created in FSM fails | |
Error when create activity using non-default business roles | |
Incorrect exception handling when deletion of attachment from FSM fails | |
ItemWarehouseLevel information not sent from ERP to FSM | |
3001263 - note for ECC component PACG 110 3001261 - note for S4 component S4PACG 100 | Connector event 'notification save' sometimes is not triggered |
Missing assignments of ‘orginfo’ and ‘userrole’ objects in setup program | |
Stock Item Duplicate quantity sent to FSM | |
Wrong operation reference during inbound GOODREC_IN processing | |
Short dump during read of a network order's component within inbound GOODREC_IN processing | |
CX_SY_MOVE_CAST_ERR raised when Item is sent to FSM | |
'Activity changed' event is not triggered when users' fields are updated | |
Teams maintenance transaction dumps at save 'LOAD_PROGRAM_NOT_FOUND' | |
Equipment replacement terminates with dump | |
Item IDOC does not trigger to FSM if entries not present in MARD table | |
Incorrect params used in /PACG/ECM_CL_X_WRAPPERS=>BAPI_IE4N_INSTALL | |
Service Call user status is not updated when changed in FSM | |
UDO report for note 3010934 Dump during processing of inbound user IDOCS | |
CX_ST_DYN_CALL_ILLEGAL_TYPE short dump during posting of material document | |
When using BDS attachments filename is not saved | |
Controlling document not created for inbound mileage posting (missing date) | |
All employees sent to FSM despite the flag saying only those with corresponding sap user should be sent | |
Incorrect controlling document created for inbound mileage posting (wrong duration) | |
GOODREC_IN dumps due to incorrect data type | |
Team maintenance dumps when saving | |
"Assertion failed" error occurs when events are triggered with empty key | |
Incorrect reference to removed reservation during material document creation | |
Connector terminates with dump in method /PACG/ECM_CL_D_ACCESS=>GET_MATERIAL_TYPES | |
When operation is created based on inbound activity functional location is ignored | |
Processing of activities having longer duration terminates with shortdump | |
The functional location is truncated in the outbound activity | |
Incorrect unlocking in the FM /PACG/ECM_BAPI_EC4_ACTI_CHANGE | |
Error time booking with start time at 00:00:00 | |
Wrong goods movement when returning material to stock | |
Missing default customer determination during service order generation from the notification origin | |
Error when adding new user in transaction /PACG/ECM_USER | |
The BAPI_ALM_ORDER_GET_DETAIL can impact loaded statuses | |
Service call's subject gets truncated | |
Service call subjects gets joined with the first line of remarks | |
Short dump during inbound activity processing - incorrect duration calculation | |
Short dump during duration conversion - Inbound Activity | |
Archiving object FI_ACCRECV deletes not all archived entries after FSM Connector upgrade | |
Incorrect execution stage is set when Activity gets cancelled | |
/PACG/ECM_TRIG_RGPPG replicates irrelevant data to FSM | |
Service call address not updated when incident reported with FSM Self Service | |
Incorrect batch assignment of the non-batched material | |
User ID is set incorrectly in the aoutbound User Role message | |
Sending equipment and end date on equipment level may impact performance | |
Short dump during outbound equipment characteristic UDF processing (Date format) | |
Unnecessary masking of "&" and "<" during checklist position processing | |
Address not sent with service order when special stock not found | |
Assertion failed - Activity Event triggered without activity number | |
/PACG/ECE_ACTIVITY_TRANSFER dumps when executed in the background | |
Optional activities sending during migration | |
DB deadlock in hash handling | |
Break time duplication error for worktime over 2 days | |
Reserved Material cannot be consumed due to missing stock quanitity |
If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.