You need to create 3 IDoc adapters with 3 distinct RFC destinations and assign them in corresponding receiver agreements. When the time-zone of sender systems is known as design time, it becomes simple. The RFCs will be on system users (created in ECC) on separate time-zones (AST or as agreed, GMT and AU-VIC or as agreed).

Let’s call them RFC_NA, RFC_GMT & RFC_AU. Solution: In this case, it is required to create 3 additional RFCs in PI. System C is on AU-VIC (Australia) time-zone System A is on CST (North America) time-zone Let’s consider a scenario below where 3 systems are on different timezones. Apart from the fact that this helps in monitoring, it might also have to do with business requirement for Order creation date/ time, Goods receipt posting, subsequent inventory reconciliation and invoicing. For this, it is imperative that the IDocs are posted with User profiles of respective time-zones.

It is required that the IDocs are posted in ECC with respective time-zones of the sender systems. Many projects use PIAPPLUSER while creating the RFC while some other projects create System user with specific roles for this purpose. The time of posting of IDoc is actually dependent on the user profile used while creating the RFC. In a multi-phase global SAP implementation for third party to IDoc scenarios, there can be a requirement that the IDocs are posted in the time-zone of the sender systems.įor the SAP inbound IDoc scenarios which are through PI, IDocs are posted through an RFC destination of Type H created in PI to access SAP R/3 system.

Ikingssgc time zone account creation