Internal Order or Project WBS- Part1

In SAME-SYSTEM, when we migrated from I/O to PS :   migrate or transfer data from Internal Orders (IO) to Project System (PS) in SAP. This is a common scenario when organizations start with internal orders for tracking costs but later want to move to the more structured WBS Element / Network setup in PS.

Here’s a clear breakdown:

🔹 Why migrate from Internal Order (IO) to Project System (PS)?

  • Scalability: Internal orders are good for simple cost tracking, but PS gives hierarchical structure, scheduling, resource planning.
  • Integration: PS integrates with MM, SD, PP, HR, CO.
  • Reporting: Detailed project reports (costs, commitments, revenue, progress).
  • Control: Budget, availability control, project settlement rules.

🔹 Approaches for Migration

1. New Implementation – Manual Master Data Creation

  • Create WBS elements / Networks in PS.
  • Close Internal Orders (KO02 → Set “Deletion Flag” / “CLSD”).
  • Migrate balances using reposting transactions.

2. Data Migration via Reposting Tools

  • Master Data Migration:
    • Internal Order → WBS (use LSMW / LTMC / BAPI to create WBS elements).
  • Transaction Data Migration:
    • Open Commitments: Recreate PRs/POs against WBS.
    • Actual Postings: Transfer using repostings in CO.

Key transactions:

  • KB11N – CO reposting line items (manual transfer).
  • KB61 – Reposting of revenues.
  • KSV5/KSU5 – Assessments/Distributions.
  • CJ88 – Project settlement (once PS is live).

3. Technical Migration with BAPIs

  • For bulk historical migration, use:
    • BAPI_INTERNALORDER_GETDETAIL (extract IO data).
    • BAPI_PROJECT_MAINTAIN / BAPI_BUS2001_CREATE (create PS WBS/Networks).
    • BAPI_ACC_DOCUMENT_POST (for balances transfer).

🔹 Step-by-Step Example Migration Flow

  1. Preparation
    • Identify list of IOs to be converted.
    • Map IO fields to PS objects (Responsible CCtr, Profit Center, Settlement rules → Receiver).
  2. Create Projects/WBS
    • Use CJ20N or migration tool.
  3. Migrate Open Commitments
    • Cancel PR/PO from IO, re-create under WBS.
  4. Transfer Actual Costs
    • Use KB11N to repost from IO → WBS.
    • Alternative: Settlement from IO to WBS (KO88, if allowed).
  5. Close Internal Orders
    • Status CLSD/Deletion flag after migration check.
  6. Future Postings
    • Redirect FI/CO/MM postings to WBS instead of IO.

🔹 Accounting Entries Example

Say IO had an expense of 10,000 booked:

At IO stage:

Dr Expense A/c      10,000     Cr Vendor A/c           10,000     (CO Object = IO 1001)  

Migration to WBS: (via reposting)

Dr Expense A/c (WBS 2001)   10,000     Cr Expense A/c (IO 1001)      10,000  

→ Net effect: IO cleared, WBS now bears the cost.

more or less similar approach can also be used for two-system approach. For Pr/PO against IO (In Legacy-system, For NEW PR/PO (of remaining Balance) against Project-WBS will have to be created in S/4HANA.  

=============

Pages: Page 1, Page 2