General presentation

Objective of the application

Describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO

The iCare application was migrated from PQ1 to WBP in October 2017 by PQ1 decommissioning project and consist in developing a BW flow and Function Modules, regarding Accounts, Pending Orders and Overdues to be sent to Salesforce (SF). 

Function Modules(FM) are used, through multiple type of operations, to synchronized Salesforce & BW.

WebMethods (WM) is used as a Middleware between both .

Tool and IT leaders of the application are:

• RtR : Guillaume Thevenet (Process Chain & Overdue's DSO)
• OtC : Craig Wanamake (Pending orders & Account on BW)
• Salesforce : Emmanuel Gaheri
• WebMethods : Reiner Hellstern
• Project manager : Anon Kasemvilas
• Developer:  Dan Messas

Usage information

This project have only Salesforce users.

History

This project consist on a migration of existing Function Modules and BW objects from PQ1 to WBP.

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Authorization objects

Authorization to access report is managed by Salesforce because the reports are in salesforce platform.  For BW, it is only preparing data on tables and DSO in order to load to SF

Dataflow overview

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B8xksr4mF3-aZFNVY3V3TF9DVFE

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

As WebMethods is used as a Middleware, it triggers every steps of each application (BW, SF), and send data from a side to the other.

1. Accounts : FM Z_ZSF_GET_ACCOUNT_DATA

1. Operation U : WM (WebMethods) extract from SF (Salesforce) the account list that are already synchronized and send it ton BW through de FM. On BW side in the ZSF_ACCOUNTS table, all entry are flagged as "Deleted". If SF ID in found, the flag is unchecked.
2. Operation N : WM extract from SF the account list that are not yet synchronized and send it to BW. It will fill the BW table with the SF ID. Then it generate the S_SF_UPDATE_TIME job to run PF1 Function Z_ZSF_CHECK_UPDATE_TIME which will read PRS table ZZR_CUST_CRM to map SFDC ID with Sold to. PF1 Function will get Credit information to be inserted in BW table ZSF_ACCOUNT and then Copy PRS table ZZR_CUST_CRM to BW table ZSF_SOLDTOS Fills BW tables ZSF_ACCOUNTS and ZSF_SOLDTOS. Marks entries as ‘must be sync’. Table ZSF_PRODUCT is filled in with SFDC Products.
3. Operation S : BW reads entries from table ZSF_ACCOUNTS with flag ‘must be sync’ and where delete is null. SF receives response from BW (through WM) and include entries that are included in the temporary mapping to be updated. Sends the Ack to WBP (via WM) starting operation ‘A’. 
4. Operation A : BWP updates 'last sync' field of ZSF_ACCOUNTS and SF updates entries.

Other operations :

• • • Operation T :  Update the last update time from SalesForce (Variable :  WA_ZSF_LOGS)
    • Operation D :  Delete the table content (No variables)
    • Operation I   :  Init the synchronization for an ACKID (Variables :  IE_ACKID)
    • Operation H :  Init the synchronization for a date (Variables :  IE_ACKID)
    • Operation G :  Change entries in DB for test purpose (No variables)

Monitoring : 

2. Overdues : FM Z_ZSF_GET_OVD_INVOICES

The aim of the interface is to daily load the invoices in overdues from SAP into Salesforce CRM.
The scope is limited to the invoices and will present the purchase orders and the materials associated to the invoice for GBU Specialty Polymers.
The data will be automatically refreshed once a day (during the night) starts in SFDC at 02:00 CET.
Every day, all overdues data are deleted from SFDC and loaded from SAP into SFDC.
There are 5 steps :

• • 1. Process Chain : PC_SFDC_OVD_01 load the overdues in DSO DBFIAR22. At the end of the PC, FM is triggered with Operation U : 
    2. Operation U: 
       1. Empty the 3 tables ZSF_OVD_INVC,  ZSF_OVD_INVC_MAT and  ZSF_OVD_INVC_PO
       2. Then those tables are filled from DBFIAR22 DSO + Data from PF1 by calling function module Z_ZSF_GET_OVD_INVOICE
       3. Update X on field 'Must be sync' flag on ZSF_OVD_INVC when returncode = 00 and SF_ID <>""

          1. Returncode of the function module meaning

             Return Code	Meaning
             00	OK
             01	Can't find information of FI document header (BKPF)
             02	FI doc does not have type VBRK (BKPF)
             03	Can't find information in billing document (VBRK)
             04	Can't find information from the items of the billing doc (VBRP)
             06	Can't find information from PO order (VBAK)

    3. Operation S : 
       1. BW send ZSF_OVD_INVC when  returncode = 00 and SF_ID <> '' and MUSTBE_SYNC = 'X' to SF by table TI_DATA  as parameter
       2. BW update ACKID fields = current date and time on table  ZSF_OVD_INVC
       3. WM deletes all the overdues in SF and update data in SF
       4. Once WM synchronize completed with SF. WM call operation A
    4. Operation A : 
       1. BW update the  LAST_SYNC field in the overdues table ZSF_OVD_INVC (from current date of BW).
       2. BW clear MUSTBE_SYNC on table ZSF_OVD_INVC
    5. Operation I : SF send ID of overdue to BW the couple ID/External ID and BW will map ID with they key to update SF_ID of 3 tables ZSF_OVD_INVC,  ZSF_OVD_INVC_MAT and  ZSF_OVD_INVC_PO
    6. Operation P : BWP send to SF informations about material & PO.
       1. BW send ZSF_OVD_INVC_MAT when SF_ID_OVD <>'' and ID_SF_MATGROUP <> '' and to SF by table TI_MATKL  as parameter
       2. BW send ZSF_OVD_INVC_PO   when SF_ID_OVD <>'' and BSTNK  <> '' to SF by table TI_PO  as parameter
          
          

Other Operations : 

• • Operation J :  Update by job (No variables)

  • Operation U :  Update data from the ODS (No variables)

  • Operation H :  Init the synchronization for a date (Variables :  IE_ACKID)

  • Operation R :  Delete table contents (No variables)

Monitoring :

In BW:  

• • Check job of process chain PC_SFDC_OVD_01
  • Table ZSF_OVD_INVC has to be 
    • LAST_SYNC and ADCKID have to be updated for the date of sending/loading
    • MUSTBE_SYNC has to be empty 
    • Return code should be 00 for some records 

See 'Dependencies with other applications > Salesforce' Chapter.

3. Pending Orders : FM Z_ZSF_GET_PENDING_ORDERS

 This interface has been done to provide Sold and Pending information from SAP and link it with Salesforce Accounts.
The Scope is limited to Specialty Polymers Customers.
The data will be automatically refreshed once a day (during the night) - start in SAP at 11:00 pm CET (00:00 CEST) and starts in SFDC at 10:00 CET (11:00 CEST).
There are 3 steps (Operations) :

1. 1. Program Z1F_ZSF_PEND_ORDERS_DATA_V3 is triggered on PF1 to fill ZSF_OPEN_ORDS table on WBP.

   2. Operation S : WebMethods reads entries from table ZSF_OPEN_ORDS to check if the first line contains number of records. SF delete all entries and receives response and creates new entries, then sends the Ack to WBP, starting operation ‘A’.

   3. Operation A : WBP receives ack from WM and Updates ACKID and LAST_SYNC fields of ZSF_OPEN_ORDS. SF updates entries.

Other Operations :

• • • Operation J : Update by job (Variables :  i_origin)
    • Operation U :  Update data from the query (Variables :  i_origin)
    • Operation H :  Init the synchronization for a date (Variables :  IE_ACKID)
    • Operation I :  Put entries for the be synch (Variables :  i_origin)
    • Operation B :  Copy Backup Table to S&P Table (No variables)
    • Operation C :  update table S&P from PF1 (No variables)

Monitoring : 

    In SAP PF1_020 :

   In SAP WBP_400 :

Function Module Variables :

I_ORIGIN - Possible values are : 'P' (Perform actions) and 'S' (Simulation)

I_OPERATION : Different operations previously explained ('S', 'A', 'I', 'P' for Overdues)

Dependencies with other applications

Salesforce : is the CRM which receives data from SAP (PRS/PF1 → BWP → SF)
Monitoring :

• • Check if SFDC job is complete with success : Setup → Jobs → Apex Jobs → Apply View: [Select a View]
  • For more detailed info, please refer to Document : IS - Appl - CRM - Monitor Interfaces
  • In case of failure : please contact : fas-salesforce@solvay.com 

WebMethods : is the middleware which triggers the step from SAP and SF.

• • In case of failure : create a freshdesk ticket and assign it to IS-CAPG-ERP group

Data loadings

Info providers and objects loaded

There is only one process chain on this project. It's for the overdues : PC_SFDC_OVD_01. It loads data from DSOs DBFIAR02 & DBFIAR16 to the newly created DSO : DBFIAR22.

Loading frequency

The process chain is running every day at 2AM.

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

The reports are available only on Salesforce

Main queries

List the most important and complex queries only with a link to the documentation

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016