Here is the Standard Operating Procedure (SOP) for the INT6105b (Monthly Reporting) integration.

SOP: INT6105b - Monthly Reporting Budget Data Inbound

1. Integration Overview

• System Name: INT6105b (Monthly Reporting) Budget Data Inbound from BRAINs

• Purpose: To import monthly "Reporting Forecast" budget data from ProfitSword/BRAINS into Workday.

• Source: ProfitSword/BRAINS (via SFTP).

• Frequency: Monthly (processing "6-period/half year" forecast files: 01-06, 07-12).

• Integration Type: Workday Studio Assembly (Custom).

• Web Service: Import_Budget_High_Volume_Request (Financial Management v41.0)
  .

2. Configuration & Attributes

The integration relies on specific attributes configured on the Integration System to determine where data is loaded.

Integration Maps:

The system uses Internal-to-External maps to translate legacy codes to Workday Reference IDs.

• Translation Code to Cost Center: Maps the TRANSLATION column to a Cost Center WID.

• Company Translation Code to Outlet: Maps a concatenated Company-Translation string to an Outlet WID.

3. Processing Logic

Step 1: Retrieval & Initialization

• The integration triggers via the Monthly_Reporting service.

• It executes the Parms2 mediation, setting the run mode to 'Reporting Forecast'.

• The file is retrieved via the INT6105b_Get_File retrieval service.

• Validation: The process verifies the file size is greater than 0; otherwise, it logs an error "No file found or empty file"
  .

Step 2: CSV Parsing & Mapping (Apply_Maps.xsl)

• The raw CSV is converted to XML
  .

• Row Filtering: Rows where both Debit and Credit are 0 or empty are discarded
  .

• Cost Center Logic: If TRANSLATION is present (and not 'TRA000'), the system performs a reverse lookup against the 'Translation Code to Cost Center' map. Otherwise, it uses the raw COST_CENTER value
  .

• Outlet Logic: If TRANSLATION matches specific prefixes (e.g., 'TRA200'), it performs a reverse lookup against 'Company Translation Code to Outlet' using the key format COMPANY-TRANSLATION
  .

• Numeric Cleanup: Debits and Credits are normalized to '0' if they are empty or invalid
  .

Step 3: Currency Merging (Merge_Currency.xsl)

• The integration runs a Workday Report Company_Currencies (INT6105 - Get Company Currency).

• It looks up the Company_Ref_ID from the incoming file against the report data to assign the correct Company_Cur_ID (Currency) to the transaction row
  .

Step 4: SOAP Generation (Create_Group_XML_2.xsl)

This step creates the Import_Budget_High_Volume_Request.

• Grouping: Data is grouped by COMPANY, POSTING_INTERVAL, LEDGER_ACCOUNT, COST_CENTER, OUTLET, SPEND_CODE, REVENUE, JOB_TITLE, MEAL_PERIOD to aggregate lines
  .

• Import Mode: Hardcoded to INCREMENTAL_ADD_ONLY
  .

• Fiscal Period Mapping: The POSTING_INTERVAL (e.g., 202301) is parsed. The first 4 digits become the Year, and the last 2 digits map to the YE_Dec_PXX_Mon ID (e.g., '01' maps to YE_Dec_P01_Jan)
  .

• Ledger Account Logic:

  • If LEDGER_ACCOUNT starts with "ST", it maps to parent type Statistics.

  • Otherwise, it maps to parent type HHM
    .

• Worktags: The logic systematically maps Cost Center, Spend Category, Revenue Category, Custom Organizations (Job Title/Outlet), and Custom Worktag 5 (Meal Period) only if the values are not empty
  .

Step 5: Submission & Verification

• The request is sent via WorkdayOutSoap
  .

• The integration enters a DoWhile loop to poll the status of the import process until it returns 'Completed', 'CompletedWithErrors', or 'Failed'.

4. Input File Specification

1. COMPANY

2. MEMO

3. POSTING_INTERVAL (Format: YYYYMM)

4. LEDGER_ACCOUNT

5. COST_CENTER

6. SPEND_CODE

7. REVENUE

8. JOB_TITLE

9. OUTLET

10. MEAL_PERIOD

11. BANK_ACCOUNT (Ignored in mapping)

12. INTERCOMPANY

13. TRANSLATION (Used for Cost Center/Outlet lookups)

14. DEBIT

15. CREDIT

5. Troubleshooting & Error Handling

6. Maintenance

• Integration Maps: Ensure Translation Code to Cost Center and Company Translation Code to Outlet are updated when new codes are added in Brains/ProfitSword.

• Fiscal Periods: The XSLT hardcodes periods 01-12 to YE_Dec naming conventions
  . If the fiscal year definition changes (e.g., to a non-December Year End), Create_Group_XML_2.xsl must be updated.