SAP Testing Strategy: Unit → SIT → UAT → Regression → Cutover

A successful SAP go-live depends on more than correct configuration. Testing helps confirm that the system, end-to-end processes, and business results are ready.

The testing journey

1. Unit testing — Does each piece work?

Test individual configurations, developments, or process steps.

Usually done by: Functional and technical consultants.

2. SIT — Do the connected processes work?

System Integration Testing checks end-to-end processes across SAP modules and systems.

Examples:

• MM → FI
• SD → FI
• PP → MM

3. UAT — Does it meet business needs?

User Acceptance Testing lets business users run realistic scenarios and confirm the solution supports their requirements.

Check not only that the steps work, but also that the outcomes are right—for example, financial postings, inventory balances, procurement and sales results, controls, and reports.

Key outcome: Business acceptance or sign-off.

4. Regression testing — Did a change break anything?

After a fix, configuration change, or new development, retest important existing processes to check that they still work as expected.

5. Cutover testing — Are we ready to go live?

Validate the activities needed to move into production. This may include:

• Data migration
• Master data and open transactions
• Period-end or closing activities
• Mock cutover or dress rehearsal

Easy way to remember

• Unit: Does each component work?
• SIT: Does the end-to-end process work?
• UAT: Does the solution meet business needs?
• Regression: Did our changes affect existing processes?
• Cutover: Are we ready for go-live?

The goal: The system works, the business process works, and the business results are accurate. ✅

Testing stages and responsibilities may vary by project; align the approach with the project team and business stakeholders.

Subcontracting vs. Consignment in SAP MM

 Both processes involve a supplier, but the key difference is who owns the stock and when the supplier is paid.

	🔵 Subcontracting	🟠 Consignment
What happens?	You provide components; the supplier processes them and returns a finished product.	The supplier keeps stock at your site; you pay only when you use it or transfer it to your own stock.
Who owns the stock?	Your company owns the components sent to the subcontractor.	The supplier owns the consignment stock until it is consumed or transferred.
PO item category	L – Subcontracting	K – Consignment
BOM required?	Usually needed to propose the components in the PO.	No
How is the supplier paid?	Invoice for the processing charge, typically via MIRO.	Settlement for consumed or transferred quantities via MRKO.

🔵 Subcontracting: supplier processes your components

1. Prepare master data
   Create or check the material and supplier (Business Partner) records.

2. Create a BOM
   Use CS01 to define the components needed to make the finished product. A purchasing info record may be used, but is optional in the standard process.

3. Create the subcontracting PO
   Use ME21N and select item category L – Subcontracting. Check the Components tab to review the components proposed from the BOM.

4. Send components to the subcontractor
   Post the transfer using movement type 541. The components remain company-owned, but are shown as stock provided to the subcontractor.

5. Receive the finished product
   Post the goods receipt, typically with movement type 101. Component consumption is generally posted automatically with movement type 543.

6. Pay the subcontractor
   The PO price is for the supplier’s processing service—not the value of the components. Post the supplier invoice in MIRO. Whether invoice verification is goods-receipt-based depends on the PO and business setup.

🟠 Consignment: supplier-owned stock is held at your site

1. Prepare master data
   Create or check the material and supplier (Business Partner) records.

2. Create a consignment purchasing info record
   In the standard process, this holds the price used for settlement.

3. Create the consignment PO
   Use ME21N and select item category K – Consignment. A BOM is not required.

4. Receive the consignment stock
   Post the goods receipt, typically with movement type 101 and special stock indicator K. The stock is recorded as supplier-owned; the receipt itself normally does not create a stock-value accounting posting.

5. Use or take ownership of the stock
   Examples include:

   • 201 K – Issue to a cost center
   • 261 K – Issue to a production order
   • 411 K – Transfer consignment stock to your own stock

6. Settle with the supplier
   Use MRKO to settle the quantities consumed or transferred to company-owned stock. Consignment settlement is not normally processed as a standard invoice through MIRO.

Note:

• Subcontracting: We provide components; the supplier returns a processed product.
  541 → 101 / 543 → MIRO
• Consignment: The supplier owns the stock until we use it or take ownership.
  101 K → consumption or transfer → MRKO

Essential SAP Transaction Codes for Production Support and Critical Issue Analysis

T-code	Purpose
SU01D	Display a user’s account details, assigned roles, and user status.
SUIM	Search and report on users, roles, profiles, and authorizations.
SE10	Manage transport requests and tasks, including reviewing and releasing them.
SM37	Monitor background jobs: status, schedule, job log, and spool output.
SE37	Display and test function modules, including RFC-enabled modules.
SA38	Execute an ABAP report by entering its program name.
SE16H	Browse and analyze table data, with filtering and additional analysis features.
SE16N	Display table contents with selection filters. Use carefully; access to sensitive data may be  restricted.
SE11	Display or maintain ABAP Dictionary objects such as tables, views, data elements, and structures.
ST22	Review ABAP runtime errors (short dumps) and their technical details.
SM21	Review system log entries, such as system events and errors.
SLG1	Display application logs for business processes and programs.
SM13	Monitor update requests and investigate failed updates.
SM58	Check transactional RFC (tRFC) calls that are waiting or have failed.
SMQ1	Monitor outbound queued RFC (qRFC) queues.
SMQ2	Monitor inbound qRFC queues.
WE02	Display and analyze IDocs, including status, segments, and errors.
SU53	Show the last failed authorization check for the current user.
SM12	Display and manage SAP lock entries. Don’t delete locks without confirming they’re stale and safe to remove.
SM50	Monitor work processes on the current application server.
ST05	Trace performance activity, such as SQL statements and RFC calls, for troubleshooting.

Looking for remote work opportunities in 2026

Here are 27 platforms that offer remote job opportunities:

-Remotive (https://lnkd.in/gUQ7vrVq)

-Toptal (toptal.com)
-Skip The Drive (https://lnkd.in/gw5cSAew)
-NoDesk (nodesk.co)
-RemoteHabits (remotehabits.com)
-Remote4Me (remote4me.com)
-Remotees (remotees.com)
-justremote (justremote.co)
-Remotecrew (remotecrew.io)
-FlexJobs (flexjobs.com)
-Remote (remote.co)
-We Work Remotely (weworkremotely.com)
-Remote OK (remoteok.com)
-AngelList (angel.co)
-LinkedIn (linkedin.com)
-Upwork (upwork.com)
-Freelancer (freelancer.com)
-Working Nomads (workingnomads.com)
-SimplyHired (simplyhired.com)
-Jobspresso (jobspresso.co)
-Virtual Vocations (virtualvocations.com)
-Stack Overflow Jobs (stackoverflow.com/jobs)
-Outsourcely (outsourcely.com)

SAP TM overview and Important Master data

 

SAP TM (Transportation Management) is the specialized engine designed to handle the physical movement of goods from point A to point B as efficiently and cheaply as possible.

For Example Siri’s Beauty Tech shipping delicate products like perfumes, creams and makeup across borders requires precision.

In S/4HANA, SAP TM has officially replaced the old "LE-TRA" (Shipments) module. Here is a high-level overview and a deep dive into the master data that makes it work.

 

1. SAP TM Overview: The "Plan, Execute, Settle" Lifecycle

Think of SAP TM as a digital "Travel Agent" for your products. Its workflow follows four main stages:

1. Strategic Freight Management: Negotiating long-term contracts and rates with carriers (e.g., DHL, Maersk).
2. Order Management & Planning: SAP TM takes Sales Orders or Purchase Orders and creates "Freight Units." It then uses an Optimizer to decide: Should this go by truck or ship? Which route is fastest? Can I combine these three orders into one container?
3. Transportation Execution: This is the "Real-time" phase. It monitors the truck's status, handles the printing of Waybills (BOL), and manages events (e.g., "Truck has arrived at the L'Oréal warehouse").
4. Freight Settlement: The financial part. It calculates exactly how much we owe the carrier based on the weight and distance, creates a "Freight Settlement Document," and pushes it to FI/CO for payment.

 

2. Important Master Data in SAP TM

Master data is the foundation. If your master data is wrong, the Optimizer will suggest impossible routes or wrong prices. We categorize TM master data into four pillars:

A. Foundational Master Data (The "Who" and "What")

• Business Partner (BP): Unlike standard MM, in TM we use specific roles for Carriers (the shipping company) and Sold-to-Parties. The BP must have the "Carrier" role to be assigned to a freight order.
• Product: The material master must include weights, volumes, and "Transportation Groups" (e.g., Fragile, Hazardous, or Temperature-Controlled).

B. Transportation Network (The "Map")

• Locations: These represent any point in the journey (Plants, Customers, Ports, or Hubs). In TM, every location has Geocoordinates (Latitude/Longitude) so the system can calculate actual distances.
• Zones: A group of locations (e.g., "All zip codes starting with 75 in Paris").
• Transportation Lanes: These are the "Roads" between two locations. It defines which carriers can drive there and which "Means of Transport" (Truck, Plane, Ship) are allowed.
• Distance and Duration Matrix (DDD): The system uses this to know it takes 4 hours to drive from Paris to Brussels.

C. Transportation Resources (The "Tools")

• Vehicle Resources: Digital versions of the actual physical trucks or containers. You define their Capacity (e.g., Max 20 tons or 33 Pallets).
• Handling Units / Packaging: Definitions of pallets, boxes, or crates used to calculate how to pack the vehicle.

D. Transportation Charge Management (The "Money")

• Scale: The variables used to calculate cost (e.g., Weight, Distance, or Number of Pallets).
• Rate Table: The "Price List." For example: 0-100km = €50, 101-200km = €80.
• Calculation Sheet: The logic for combining costs (Fuel Surcharge + Base Rate + Tolls).
• Freight Agreement: The digital contract between L'Oréal and the Carrier that links all the rates together for a specific period.

 

⚖️ Quick Comparison: Why it matters for S/4HANA Consultants

Feature	Old LE-TRA (ECC)	New SAP TM (S/4HANA)
Planning	Manual assignment.	Optimizer-based (Automatic).
Visibility	Limited tracking.	Event Management integration.
Pricing	Simple Freight Costs.	Complex Multi-modal Charges.
Mapping	No map integration.	GIS/Google Maps integration.

 

 

 

Difference between ASN and inbound delivery in SAP

SAP ASN vs Inbound Delivery

To understand the difference between an ASN and an Inbound Delivery, think of it like ordering a package from Amazon. 📦

 

1. The Simple Analogy: Ordering a Gift

• The ASN (Advance Shipping Notice): This is the Email/SMS you get from Amazon that says: "Your package has been shipped! Tracking #12345, arriving Tuesday via DHL." It is a digital "heads-up" sent by the sender to tell you what is on its way.
• The Inbound Delivery: This is the Entry in your Calendar or the Tracking App on your phone where you are waiting for the package. It is the internal record you use to manage the arrival once the truck pulls up to your door.

 

2. In the SAP World (The Professional View)

What is an ASN? (The Message)

An ASN is an electronic document sent by a supplier to a customer. In SAP, this is usually received as an IDoc (an electronic message).

• Sender: The Vendor (Supplier).
• Content: It tells you exactly what is in the truck: the quantity, the batch numbers, the delivery date, and even how it’s packed (e.g., Pallet 1 has 50 boxes).
• Purpose: To give the warehouse time to prepare for the arrival.

What is an Inbound Delivery? (The Document)

An Inbound Delivery is a document inside your SAP system (Transaction VL31N).

• Owner: You (The Customer).
• Purpose: It is the "working document." When the truck arrives at your L'Oréal warehouse, the warehouse staff don't scan the Purchase Order; they scan the Inbound Delivery.
• Function: It is used to record the Goods Receipt (GR), perform quality checks, and put the items away on the shelf.

3. How They Work Together: The Workflow

In a high-tech environment like Global Beauty Tech, the process is automated:

1. Step 1: You send a Purchase Order to a vendor.
2. Step 2: The vendor packs the goods and hits "Ship" in their system.
3. Step 3: Their system sends an ASN to your SAP system.
4. Step 4: SAP receives the ASN and automatically creates an Inbound Delivery for you.
5. Step 5: When the truck arrives, your warehouse team uses that Inbound Delivery to scan the goods into stock.

 

⚖️ The Key Differences at a Glance

Feature	ASN (Advance Shipping Notice)	Inbound Delivery
What is it?	An Electronic Message (Heads-up).	An Internal SAP Document.
Who creates it?	The Vendor (outside your company).	You / Your SAP System (inside).
Format	Usually an EDI (Electronic Data Interchange).	An SAP Transaction/Table Entry.
Analogy	The "Your order has shipped" email.	The "Waiting for delivery" status.
Example	"I'm sending 500 shampoos in Truck A."	"Document #180055: Expected 500 shampoos."

💡 Example Scenario at Siri’s Global Beauty Pte.Ltd

Scenario: You order 1,000 liters of rose oil for a perfume factory.

• The ASN: The supplier in India sends an electronic file (ASN) saying: "1,000 Liters of Rose Oil, Batch #ROSE-2024, in 5 separate drums, is on Truck Plate #AB-123."
• The Inbound Delivery: Your SAP system receives that file and creates Inbound Delivery #8000123.
• The Arrival: Two days later, the truck arrives. Your warehouse clerk types in 8000123, sees the Rose Oil and the Batch number already filled in from the ASN, and simply clicks "Post Goods Receipt."

Summary: The ASN provides the information, and the Inbound Delivery uses that information to get the work done.