General presentation

Objective of the application

Report to be able to check the payment term for intercompany customers and vendors (with the partner codes of the company).
In SAP we have :
KNB1 - customer company viewsociété (in BW data in C_CUSTCOM)
KNVV - customer sales view in BW data in C_CUSTSAL)
LFB1 - vendor company view (to be analyzed in BW)
LFM1 - vendor purchasing view (to be analyzed in  BW)
LMF2 - fournisseur vue achats (à analyser coté BW)

Usage information History 

History

           In May 2020, this data flow and the report are created, In order to have all payment terms used by the vendor/customer accounts by company wise that are  used  in intercompany process in PF1 & WP1 a new BW report must be created i.e., only customers and vendors whose KNA1-VBUND and LFA1-VBUND respectively are filled. 

Roles & Access

Roles and access

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

Authorization objects

List of autorisation objects mandatory for the application.

Dataflow overview

Functional and Technical rules on Workbench + Reporting

The FSD is attached in the google drive link : 

The TSD is attached in the google drive link:  

Rules & Explanations

For Customer report:

1. Get all the intercompany customers whose KNA1-VBUND ≠ blank 

2. For the above customers get the payment terms company wise ‘KNB1’  and Sales org wise ‘KNVV’

3. Link between PRS and Local Company codes is already managed in BW using PRS_050  ZZF_T001_MGT, the same should be used to map PRS company to Local company.

4. For local company get the country T001-LAND1.

    Report lines should be populated as below
   

5. For the local company, get the available customers KNB1-KUNNR and payment terms ZTERM – KNB1

   If ZTERM-KNB1 is populated then other payment terms and below fields should be marked #

   • Sales Org  KNVV-VKORG

   • Distribution Channel

   • Division

   • Terms of Payment KNVV-ZTERM

6. Lookup table TVKO Sales Organizations to identify Sales orgs of the local company.

7. Get the Distribution channel, Division and sales org. for the customer KNVV and add new rows against the customer with the Company code and payment term copied from KNB1 only for those sales orgs from rule 6

   
   For Vendor Report: 

8. Get all the intercompany Vendors whose LFA1-VBUND ≠ blank

9. For the above vendors get the payment terms company wise ‘LFB1’  and Purchase org wise ‘LFM1’ and Plant wise ‘LFM2’

10. Link between PRS and Local Company codes is already managed in BW using PRS_050 ZZF_T001_MGT, the same should be used to map PRS company to Local company.

11. For local company get the country T001-LAND1.

      Report lines should be populated as below,
    

12. For Vendor Records: 

    - Populate the payment term ZTERM-LFB1 with Vendor and Company.

                 - If ZTERM-LFB1 is populated then other payment terms and below fields should be #.

    • Purchasing Org

    • Plant

    • LFM1 –ZTERM

    • LFM2 –ZTERM

    
    

13. Lookup T001K Plant master to identify list of plants for the Company.

14. Lookup T024W to get the list of purchasing orgs associated with the plant.

15. For each combination of company-plant-purchasing org Populate the payment term ZTERM-LFM1.

16. Add rows copying  ZTERM-LFB1and LFB1-compnay against the vendor

17. ZTERM-LFM2 will be #. 

    15. For each combination of company-plant-purchasing org (ignore LFM2-LTSNR)

1. Populate the payment term ZTERM-LFM2.

• Add rows copying  ZTERM-LFB1and LFB1-compnay against the vendor

Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

The Process chain that is used is  ZPC_FIPT_01.  

Main chain : ZPC_MD_RCS_ATTR → ZPC_FIPT_01

Loading frequency

Daily

Average performance

Reporting

Queries End User Documentation

Workbook created:  BW_WBK_FIPT_001

Queries:        BW_QRY_CPFIPT01_0001 -Payment term data for Intercompany Customers  (Core Query)

                      BW_QRY_CPFIPT02_0001 - Payment term data for Intercompany Vendors  (Core Query)

Main queries

https://drive.google.com/drive/folders/1BJmsuHWeg4UD9xIxWjfeztm6OAMv_mON

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