Tasks to be completed when documenting an operation (from creation to publication)

  1. Enter the Title of the operation / page

  2. Add the following Labels

  3. Fill in all fields as described above

  4. Once the procedure is completed, ensure it is published by using the SBS-Finance approval workflow



Domain: Central Finance Processes & Compliance



Responsibility area: Guarantee Corporate Insurance Reporting


Table of contents 

By default the table of contents displays Heading 1 & Heading 2 (other levels can be added)

 


Scope

3. Remove the icon when not applicable

 

ERP

4. Remove the icon(s) when not applicable

 

Frequency

5. Remove the icon(s) when not applicable

   

  

References

6. Add the link to SAP transaction(s) (when it exists)

 

Forms

7. Insert the links accordingly and change the link text with the OP name

Accrual Object creation template

Attachments



I create the Corporate Insurance allocation cycles << >> I post the Corporate Insurance accruals final values

 

 

1. Objective and Scope

1.1 Objective of this Operation

To ensure correct data presentation.

1.2 Scope

All legal entities under the scope of Corporate Insurance Global program.

2. Definitions

Definitions should be added in the Finance Glossary 

 

3. Tasks description

3.1. I post the Corporate Insurance accruals

To run the calculation and postings:

Go to transaction ACACACT.

At the screen, enter the selection parameters: 

You can select by company code or for a range of company codes, for specific accrual object categories, or other selections.  For insurance, all SBS scope companies should be posted at the same time as a global process.  A variant can be created with the selection parameters.

  1. Company Code: Enter all SBS scope company codes or company codes to be closed
  2. Accrual Object Cat.: Enter the current year insurance category (YY_INSUR)
  3. Key Date for Accruals: Enter the current closing month end date in the Key Date for Accruals field
  4. Execution Type: 

“N” for the first time running the Accrual Engine for the month;

 “R” if it has already previously ran for that company in the month.

Accrual Engine will not duplicate postings, only process postings if there are new or changed accruals.

       5.Test Run:  Select “Test Run” to check before posting 


The next screen lists the posting to be made and any errors to be solved before running and posting:

If all looks okay, remove the “Test Run” flag and execute to create the postings.

If there are any errors, you must solve these before running to post.  Check the messages by clicking on the “Display” for lines in error to see details of the errors.  Once you have solved the error messages, remove the check from the “Test Run” box and post the entries. 

You can view the FI documents created from the Accrual Object for the monthly expense postings.  See section “Viewing and Verifying the FI Postings.”

Verifying if Posting been done in FI

There are 2 ways to verify that all documents have transferred from Accrual Object into FI postings in accounting:

  1. A specific transaction to make this check (ACACFIRECON)
  2. Go into the accrual object postings tab and check the reference document

 

1. Viewing via transaction ACACFIRECON

Go to Transaction ACACFIRECON.

At a minimum, enter the company code(s) and year on the screen:

You may also enter other criteria, but to check all postings for a company for all accrual engine objects, leave the other fields blank. 

To only see the errors, check the box for “Display differences only.”

Execute the transaction

A screen appears showing the postings in accrual engine compared to FI and the differences.  If all have been passed to accounting correctly, the differences are zero:


If there are differences, it means documents still need to be transferred to accounting, but they are blocking for some reason. Check the details of the error message to solve the error then manually pass the document to FI.  See instructions, “Manually Transferring Documents to Accounting.”

This step should be ran each month after running transaction ACACACT to expense the prepaid. Verify that all inception, inception changes, and periodic postings have all been transferred from Accrual Engine to FI.



3.2. I run the allocation cycles

All cycles are scheduled in SCMA to run at D-3. After cycles run, we have to ensure that insurance cost centers are balanced (for PF1, consider cost center EE800000IN, where EE is company establishment code; for WP1, consider the SWEEP cost center CCCC-5998, where CCCC is company code number).


3.3. I check that Corporate Insurance cost centers are settled

Go to Display Actual Cost Line Items for Cost Centers KSB1 transaction

Cost Center group: PF1 EU_INSUR for WP1 Z0006:INSUR CC or Z013: INSUR CC

Insurance CC should be ZERO and all costs allocated.


If you encounter not allocated amount within the CC- check and act accordingly to ensure data consistency.

3.4. I cross check the Corporate Insurance postings in SAP with the allocation structure file

To ensure compliance and data accuracy with the Corporate Insurance postings every closing perform data check based on the Monthly Control File.

Follow the Instruction tad to perform the check. Perform further analysis if discrepancy found. 


WHAT and HOW - Main content of the operation

The content should be mainly organized in 2 levels of Headings to ensure a proper link with the Table of Contents.

 Select the level of heading in the "Paragraph" option.