2366240 - Standard replication iFlow has FTSD one day before in the payload than what is set in the environment extensions of Boomi

This KBA is the solution for the issue described in the title.

Boomi

1. Configure the pre-packaged integration in Boomi.

2. Set the "Full Tranmission Start date" in the environment extensions. For Example:

3. Now trigger the replication and check the outbound XML, this will contain one day prior to the  date set in environment extension. example:(Taken from Org replication iFlow)

<ns1:Envelope xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/">
   <ns1:Header>
      <msgID:MessageID xmlns:msgID="http://www.sap.com/webas/640/soap/features/messageId/">61a64fc3-9aa2-4767-8c88-8b84245fed91</msgID:MessageID>
   </ns1:Header>
   <ns1:Body>
      <ns2:JobReplicationRequest xmlns:ns2="http://sap.com/xi/PASEIN">
         <MessageHeader>
            <ID>61A64FC39AA247678C888B84245FED91</ID>
            <CreationDateTime>2016-09-09T19:00:55.339Z</CreationDateTime>
            <SenderBusinessSystemID>EmployeeCentral</SenderBusinessSystemID>
            <RecipientBusinessSystemID>Target_System</RecipientBusinessSystemID>
         </MessageHeader>
         <JobReplReq>
            <FullTransmissionStartDate>2016-07-31</FullTransmissionStartDate>

The problem here is timezone difference. Any date picked on UI gets converted to UTC timestamp which might get saved as a date in the past depending on what timezone a n API user which is picking & saving the date is located.

Temporary Solution:

For now, Please adjust the Process Property date by 1 day into the future to compensate the difference between your timezone and GMT/UTC timezone. For example, if you want to run your process with date = "09/01/2016" you should set the date = "09/02/2016".

 example:

Lets look at the example where customer resides in India and wants the process property extension to trigger a execution on 2016-10-18.

If the customer in India sets the process property extension at 2016-10-18 at 12:15 AM IST on a Tuesday, Boomi will convert that to 2016-10-17 6:45 PM UTC on Monday.

That customer should set the date to 2016-10-19 to get the right date of 2016-10-18.

If the customer in India sets the process property extension at 2016-10-18 at 08:00 AM IST on a Tuesday, Boomi will convert that to 2016-10-18 02:30 AM on Tuesday.

That customer should set the date to 2016-10-18 (as the conversion to UTC does not result in the date being set to the prior day)

This is a URL that can help with the conversions:
http://www.worldtimebuddy.com/

Permanent Solution:

This is residing with Boomi, They are working on adding timezones selector to UI in order to avoid such confusions as a future enhancement.

There is no ETA on this enhancement from Boomi.

KBA , boomi full transmission start date , LOD-SF-INT-BOM , Standard SF to 3rd Party Boomi Content , LOD-SF-INT , Integrations , Problem