my sbs logo

Creation of Transfer Orders Automatically for Putaway

There are four putaway statuses for line items on an inbound delivery

  •     > Not Relevant
  • A  > Not yet processed
  • B  > Partially processed
  • C  > Completely processed


Output type WMTA must be assigned to the inbound delivery for creation transfer orders.

Step 1: Define WMTA output type for Inbound Delivery

IMG > Logistics Execution > Shipping > Basic Shipping Functions > Output Control > Output Determination > Maintain Output determination for Inbound Deliveries > Define Output types for Inbound Delivery


The  data required for output type WMTA should be assigned to access sequence 0001.

The  processing routines for output type WMTA are:

The Transm. Medium is “Special function” and assign program “RLAUTA20” and Save.

The next step is to add output type to a procedure.

Step 2: Maintain Output determination procedure.

IMG > Logistics Execution > Shipping > Basic Shipping Functions > Output Control > Output Determination > Maintain Output determination for Inbound Deliveries > Maintain Output determination procedure



The usage field determines for which are the conditions used, here it is ‘B’ for output conditions and ‘E1’ refers to inbound delivery and assigned procedure is ‘Z00001’.

In control data assign condition type ‘WMTA’


Step 3: Assign Output determination procedure to delivery type

IMG > Logistics Execution > Shipping > Basic Shipping Functions > Output Control > Output Determination > Maintain Output determination for Inbound Deliveries > Assign Output Determination procedure

Assign output procedure Z00001 and output type WMTA to Inbound delivery type EL


Step 4: Create Condition records for Inbound Delivery

SAP Easy Access > Logistics > Materials Management > Purchasing > Master Data > Messages > Inbound Delivery > Create

T.code: MN24

Result: The system finds the output type WMTA for inbound deliveries and create transfer orders for inbound deliveries automatically.

Wednesday, 26 April 2017 06:17

M&A in Oil & Gas - The technology equation

Written by

Mergers & Acquisitions (M&A) have been a steady phenomenon in the Oil & Gas industry. Primarily engaged in to drive growth, divest non-core business and sometimes for combining strengths for survival, M&A also offers opportunities to maximize profits and spread the risks. However, in most M&A deals, the focus of the participants is on financial strategy and not so much on the technology integration. And this approach is a recipe for disaster.

Today, like every industry, Oil and Gas is also going digital. Technology is becoming the systemic backbone and data - the lifeblood of all organizations. Added to this, with the uniqueness of this industry and the complexity of the processes and operations, it becomes vital to ensure synergies in the IT systems.

ERP systems in the Oil & Gas industry are tightly integrated with a plethora of legacy applications. For the M&A participants the challenge lies in handling the ownership of these applications and carving out the new ERP system post M&A.

For a newly merged entity (or the parent organization in case of an acquisition) it is important that the inherited technology applications align with the long term business goals and IT strategy. Therefore, IT organizations of both sides must engage early on in the long drawn process of M&A.

Once your IT executives start their discussions, they must cover some critical areas listed below:

  • Application Licenses: Will ERP, Middleware and other proprietary application licenses be transferred to the new entity? Will any custom built applications be omitted during carve out and ownership transfer? If so, are they business critical /used for legal reporting?
  • System carve out: Who will perform the ERP data carve out? Will historical data be omitted during carve out? If so will it have any legal ramifications? Is it critical for resolving open customer billing disputes?
  • Formulating TSA (Transition Service Agreement): Who will provide operational/ applications support and perform business critical changes during TSA period? What is the Exit clause?
  • Knowledge Transfer: Are business process documents and application system documents available? Will the parent entity provide knowledge transfer to the new support vendor?
  • Infrastructure: Can the new system be On Cloud? What is the bandwidth/connectivity, back up strategy, and business contingency planning?
  • Change Management: Due to change in business model and size there would be a need for new security roles, release strategies in procurement and modified workflows. Are business users of the carved out entity ready for this?

Oil & Gas companies can reap many benefits from this holistic approach to M&A that covers complete technology integration along with a financial focus. For instance, ITs role in formulating the TSA will protect the interests and ensure sustainability of the new entity. They can also select the SI/ AMS partners at an early stage to help in early adoption to new processes. Moreover, discussing and resolving the above mentioned areas early on will help lower the total cost of ownership for the new entity as well as ensure that Business users and external partners are better prepared to adopt quickly.

What are your thoughts on ITs role in a successful M&A? Do share your thoughts below

Wednesday, 26 April 2017 06:16


Written by

This has been a never ending debate if SAP QM can completely replace a Laboratory Information Management system. 

A typical QM-LIMS is depicted below which is based on SAP’s QM-IDI.

In this Blog I try to present a side by side comparison of these two systems.

I could be faulted for bias being an SAP QM consultant but I sincerely believe there is a valid business case for opting for SAP QM in place of COTS LIMS systems.

I attempt to give a rating of 1 to 5 for QM and LIMS against each evaluation- 1 being Lowest rank.

The biggest factor that should tilt the scales in favor of SAP-QM is inbuilt integration with ERP. This enables tighter stock control, easy traceability for batch recall and Root cause analysis. SAP QM is now  enabled with Digital signatures and Electronic batch records to comply with the GMP/CFR21 regulations of Pharma industry.

The cost of building and maintaining the interface of LIMS with SAP is very high. A middle ware is needed to translate SAP master data to LIMS data as it is most probable that the data models between the 2 systems won’t be homogeneous. This adds to the TCO.

Wednesday, 26 April 2017 06:15

SAP Programmer Analyst

Written by

Sai Business Solutions LLC., dba SBS Corp. has multiple openings for SAP Programmer Analyst.

Job Title: SAP Programmer Analyst

D    Duties:        

  • Modify existing software to correct errors, allow it to adapt to new hardware, or to improve its performance.
  • Analyze user requirements, procedures, and problems to improve SAP applications within time and cost constraints.
  • Design, develop, configure, and test SAP applications per customer requirements.
  • Review and modify SAP applications, using workflow chart and diagram and applying knowledge of SAP capabilities.
  • Consult with business users to clarify SAP program intent, identify gaps in requirements, capabilities, scheduling limitations and suggest and develop             software solutions.
  • Perform programming and configuration tasks to maintain and control the use of SAP applications.
  • Implement new SAP features in Supply Chain Management, Finance and Controlling, Customer Relationship Management, HR applications.
  • Write documentation to describe business logic, design, coding, correction and testing of SAP applications.
  • Implement SAP or support SAP Business Processes in Materials Management or Sales and Distribution or Finance and Controlling or Plant Maintenance or       Supply Chain Management or Customer Relationship Management functional areas

Minimum requirements:

Bachelor’s degree in Engineering, Information Systems, Computer Applications, Computer Information Systems, Business Administration, Business Management, Computer Science, or a related field and 5 years of post-baccalaureate progressive experience in the job offered or in SAP implementation or SAP support required.The required work experience must be in SAP implementation or SAP support.

Additional Information:

Employer’s name: Sai Business Solutions LLC., dba SBS Corp. 

Job site: 12337 Jones Road, Suite 400, Houston, TX 77070 and various unanticipated locations throughout the U.S. 

Require travel/relocation to client sites at various unanticipated locations throughout the U.S.

If you are interested in applying for this position, please mail resume referencing Job#SBS05151116 to HR Manager, Sai Business Solutions LLC., dba SBS Corp., 12337 Jones Road, Suite 400, Houston, TX 77070.  It is a regular full-time 40 hours a week position.



  • 2.gif
  • 3.gif
  • 4.gif
  • 5.gif
  • 6.gif
  • 7.gif
  • 8.gif
  • 9.gif
  • 11.gif
  • 12.gif
  • 13.gif
  • 14.gif
  • 15.gif
  • 16.gif
  • 17.gif
  • 18.gif
  • 19.gif
  • 20.gif
  • 21.gif
  • 22.gif
Legal Disclaimer | Privacy Policy | GoToMeeting | Sitemap
Copyright © 2015 SBS Corp. All rights reserved.