Blog Archive

Monday, May 29, 2017

simplifying SAP PI support project work as support person


1.Download all meta data
Prepare word document ( not image), it should be searchable by OS.
we60(idocs and zfileds) and babi( if it is standard bapi),custom rfc also.
proxy (sproxy), input and output fields. And RFC (jco) in sap pi mapping.

2. Download the all production messages 
save as excel sheet.
( this information is useful, frequencly of message flow in sap pi)

3. copy source of message mapping logic ( once notepad format is done)
(offline: helps quick search)

4. List of communication channels ( its’ further information)
Ex: JMS channel and manager name;
soap url, jdbc connection, file directory..

5. Business systems(list) and ico list. ( prepare own excel sheet)

6. EOIO messages in production (list)

7. condition editor and interface determination condition editors

8. Multi mapping mappings:

9. Important UDF logic.

10. Frequently used messages source and target sample payloads

11. all errors preparation document and solution

12. Transport process ( development, quality, production) until go live;

13. all systems owners connected to SAP PI to communicate with them.

all WSDL, XSD( provided by 3rd party), IDOC , BAPI, stored procedure or INSERT,UPDATE,DELETE operation strucutres.

Wednesday, May 10, 2017

Holding messages after system error message?

I have identified on system error message due to data error, it is Eoio message, later one more message found in holding state   , which was not found in message monitoring over view.
Now, it has been in hold state for couple of hours,
Now resend or reset sequence?
And: resend works.
Then , when do we use reset sequence? ( use of reset sequence)

1. if you see many holding messages, ( and it is eoio messages)
2. if you identify , no error with payload data.( first oldest message)
3. if it causes more holding messages for similar message type,
4. if resend button not works.

what happends: first message will be canceled and remaining messages will be resend automatically.
( so,  better to download that payload, we can resend this from sap pi , from application systems again)

Action: 1) filter all holding messages with this message type
2) find the howmany server nodes are there for this.
 ex: if you identify if this messages is run on 3 server nodes.
based on timestamp, find the oldest message, and click on reset sequence button in message monitoring.
( if you identify , messages status are delivered in zig zag fashion/ non sequencial manner)
( you need to idetify old message on next server node,( based on time and date info, you can find))
and again reset sequence button, you will be see few more messages will be in delivered status.
( similar do it for 3rd).

This information might be very very helpful, people face any situvation with holding messages in sap pi support work.

Monday, May 8, 2017

Monday, May 1, 2017

RemoteDesktop Black screen Client network remote?


Call to customer care
to restart the machine