Make Balance Sheet Reconciliation Run
- Build car files:jbs build-fca redwood/apps-fca_sap_content redwood/balancesheet-certification
- Install the following car files first, everything in partition REDWOOD which the first car will create if it doesn't exist yet and you specify no Partition
An object used to store and isolate objects.:
- fca_modules.car
- fca_content.car
- fca_sap_content.car
- balancesheet-certification.car
- (bsc_convert.car) (not needed in general)
these first 2 steps are not necessary when running using run-redwood-platform up --robotics-on-prem local-99
- In User Settings, set your email address
- Run System_Mail_Configure
- Create SAP Environment for SAP System DEC and start associated Process Server
Process servers are used to execute processes..
- “new SAP System…”
- Partition REDWOOD
- RFC Connect String: ASHOST=vdec.sap.internal SYSNR=00 TRACE=0
- Add XBP
- Client number: 800
- Set Username and password (Note
SAP and Redwood use a note system to communicate important pieces of information to their customers. You can access SAP Notes at https://launchpad.support.sap.com and Redwood Notes at https://notes.redwood.com/<Number>. Jochem: I got mine by asking Ed)
- Enabled, Default Client
save
- add the SAP_MaxSpoolSize parameter with value = -1 to the created process server (-1 means, no maximum)
- start the process server
- Create Rule Chain for usage in BSC chain by importing attached (below this itemized list) PettyCash car file.
- Run FCA_SAP_OrgStructure_Synchronize.
This imports the structure for <current year>, you can also for instance import a bunch of years by setting the Range of Fiscal Years parameter instead. To for instance 2000:20XX, make sure current year is in there.
- Run FCA_BSC_Schema_Configuration (no need to set parameters)
- In the Table
An object used to store values; much like a table in a database or a spreadsheet in Microsoft Excel. FCA_ApplicationCustomizing, change the value of “FPA_User_Who_Runs_Task” to “RfcUser”
- Run FCA_SAP_UserDetails_Synchronize
- Create a chain from Template FCA_FPA_TD_GL_Account_Certification_Template:
- Use Application
An object used to group objects like process definitions and chains. CUS_FCA
- Name it
- no further modifications needed
- Use Application
-
- Go to the Process
A process is a Process Definition that is submitted into a queue. When users request the execution of a chain, a process server creates a record in the Job table, calculates the start time and sets the status to Assigned. Orchestrator
- Create a new Process List;
- Add process you just created Process List (right mouse click),
-
Add the following values in the property screen to the right
- save
- Go to the Process
-
In Process Orchestrator ‘go back to overview’ and submit the process list you just created by setting the following parameters.
Use:
- Close date = end of current month
- Fiscal period = current month number with zero’s preprended so it has string length 3
- Close Fiscal Year = current year
-
You should receive an email when everything went right, click on the mail in the message to open BSC UI. The messages will be also found in Inbox. The submitted process with children and potential indications of problems can be found in the process monitor.
Home Screen
To add BSC Workbench to your home screen,
-
Duplicate the Home_Modules table
-
rename it CUS_Home_Modules
-
clean the parent application field
-
add this line:
Key | Name | Description | Order | Source | Target | Type | Role | Icon Name | Parameters |
---|---|---|---|---|---|---|---|---|---|
8 |
Redwood_BalanceSheet_Certification |
BSC |
8 |
REDWOOD.Redwood_BalanceSheet_Certification |
inline |
ep |
|
generic2 |
|
Bonus
- When running through docker / run-redwood-platform I use robotics-on-prem because --robotics-cloud makes you set a spool-host for the SAP system.
- In the orchestrator task, use G/L accounts 1-999999 to get a REALLY large certification (300000+ line items).
Troubleshooting
- After submitting the Orchestrator list, some of the started processes get stuck in dispatched and queued for a long time:
- It was recommended to start/stop the SAP process server.
- Didn't work for me but a fresh install of the whole thing did (might be related to incorrect settings of the SAP system environment).