Om
During
my support activates in SAP PI, I need to identify the failed messages in
message monitoring.
If
any failed messages that are due to no value mapping entry and there would be
one fix required to avoid this error at SAP ECC side.
until
we fix this change in ABAP , we could not wait for rest of entries/row (xml
file) where data is not related to this error. we are supposed to move the data
from sap pi to target system by skipping error entries in xml file ( by manual
correction).
After
getting firefighter id/support id, (manager approval and basis involvement to
get this), we can use test option in sap pi to reprocess correct xml file to
target system (production).
Other
challenges
1.
Support option supports up to 11887 entries only, if the payload has more than
this number entries/rows, we could send entire xml files to target. it
throws mapping error again in monitoring page of sap pi.
What I did ;-)
I
simply split the corrected xml file into two files, each file has less than
11887 rows.
(by
adding required tag start and end of xml file, like namespace and end tag)
No comments:
Post a Comment