Visit the SAP Forum

Languages : English | Dutch | French | Portugese | Italian

Get 30,000 Interview Questions & Answers in an eBook.

Interview Success Kit - Get Success in Job Interviews

Send your Resume to 6000 Companies
India's Best Web Hosting Company

Define Status of Supply Relationships

Home »SAP Quality Management » Supply Relationships

In the status profile, you can specify that the delivery of a material from a vendor must pass through a number of statuses, for example:

  • Model series 
  • Preliminary series 
  • Regular delivery 
You can assign different inspection types (with corresponding task list usages) to a status. The system then selects the appropriate inspection types and inspection plans based on the status of the supply relationship.

Before setting the IMG, you should :-

1.   Determine whether the supply relationships must pass through certain statuses and if this is the case, maintain the 
      corresponding status profiles for the object type QINF.
2.   If necessary, assign aninspection type (which indirectly assigns atask list usage ) to the statuses in the profiles.
3.   Store the status profiles in the quality info records (QM control in procurement) for the relevant materials, vendors and 
      plants, and set the current statuses for the supply relationships.

IMG Settings :-

Maintain status profiles in 'BS02'.

Assign delivery status for inspection type in 'SM30 - V_TQ32A'.

Tracking the Status

Each status profile must contain an initial status for newly created supply relationships. You can also define additional statuses that can be linked together in a status sequence. You can link all of the statuses together or only selected ones. You do this by assigning status numbers to the statuses and by defining a highest and lowest status number for each status in the sequence.

If a supply relationship is currently in such a status sequence, the system will only allow one current inspection lot to be created for each status; that is, it will not allow any further goods receipts until the usage decision is made for the current lot.
When you make a usage decision to accept an inspection lot, the system sets the next status in the status sequence. This is repeated with every successive usage decision, until the last status is reached. If an inspection lot is rejected, the current status is retained.

You can also set a status manually.

Inspection Type Determination

You can assign an inspection type to each status.

When an inspection lot for a goods receipt is created automatically, the system selects the inspection type that is assigned to the next status and not the inspection type that is assigned to the current status. See example!

If there is no inspection type defined for the next status in the sequence or if the last status has been reached, the system chooses the inspection type that has been defined as variant 01 or as the preferred inspection type for inspection lot origin 01.

You can only control the inspection type in this way within status sequences. If you set the individual statuses in the quality info record manually and they are not contained in a status sequence (that is, the statuses do not have status numbers), no control is exerted when the system creates inspection lots for goods receipts. You must create the corresponding inspection lots manually and select the inspection type yourself. Authorization Control

The user, who carries out the goods receipt postings requires authorization for the status change to the supply relationship. 

If no authorization exists, the system selects the preferred inspection type or the inspection type that is defines as variant 01 for inspection lot origin 01.

You must therefore assign all users that are involved in creating inspection lots at the procurement stage, authorization for the object B_USERSTAT and the object type QIN. 

For Example:

Status profile '*'
Object type 'QIN'
Authorization key either ' ' or '*'
Activity '*'

When you define the object type as 'QIN', this ensures that the user only has authorization to set the user status in inspection lot processing.

If the last status in a sequence has not been reached, you cannot post any further goods receipts between the creation of an inspection lot and the usage decision. You can overcome this problem in the following way. Have the goods receipt posted by a user, who has no authorization for the object B_USERSTAT or the object type QIN. If this authorization is missing, the system allows another goods receipt posting and chooses the usual inspection type at inspection lot creation.

Example :-

The delivery client 000 contains a processing example with a model and replicate sample that are subject to a more thorough inspection than a regular delivery.

ONo.   Status Ini Min Max Inspection type
1 0001 Supply rel. created X 1 5 ' '
2 0002 Model 2 3 0101 Model inspection
3 0003 Pilot series 2 4 01 Goods receipt insp.
4 0004 Regular delivery 1 4 ' ' -> 01 GR inspection
5 0005 Replicate sample request. 6 ' '
6 0006 Replicate sample 6 7 0101 Model inspection
7 0007 Production series 5 7 ' ' -> 01 GR inspection

Once you have entered the status profile in the quality info record for the supply relationship, the system automatically sets the initial status "Supply relationship created" and updates the status after each successful goods receipt inspection, starting with the status "Model" until the last status in the series "Regular delivery" is reached. If an inspection lot is rejected, the last status is retained. For the status "Supply relationship created", the system selects the inspection type "Model inspection" that has been defined for the next status in the sequence "Model" and searches for an inspection plan with the task list usage described in the inspection type.

If you want to inspect a replicate sample, you have to set the "Initial status" in the quality info record and then the status "Replicate sample requested". 

At the next goods receipt, the system then creates an inspection lot with the inspection type defined for the replicate sample and searches for an inspection plan with the task list usage described in the inspection type. 

Once the inspection lot has been completed and given the valuation "Accepted" at the usage decision, the status of the info record is changed to "Regular delivery".



S A P - R E S O U R C E S

Get Free SAP Resources:

Are you looking for:
  • SAP Jobs
  • Free SAP eBooks
  • SAP Softwares
  • SAP Tutorials
  • ERP Implementation Examples
Enter Email Address:
(Enter your email address above and we will instantly send you the download link to you, when you confirm your email.)
Search SAP Resources:
discussionDiscussion Center


Yahoo Groups
Y! Group
Sirfdosti Groups
Contact Us
Sign in

User Name:
Forget password? | Register


Get 30,000 Interview Questions & Answers in an eBook.

Interview Success Kit - Get Success in Job Interviews

Send your Resume to 6000 Companies

SAP Resources

  • SAP Articles
  • SAP Books
  • SAP Certifications
  • SAP Companies
  • SAP Study Materials
  • SAP Events
  • SAP Faqs
  • SAP Jobs
  • SAP Job Consultants
  • SAP Links
  • SAP News
  • SAP Sample Papers
  • SAP Interview Questions
  • SAP Training Institutes
    SAP Tutorial

  • Introduction
  • SAP History
  • SAP Facts
  • SAP Tables
  • SAP Function
  • SAP Report
  • Reasons To Use SAP
  • SAP Landscape
  • SAP Transaction Code
  • SAP Lotus Notes Integration
  • Business Connector and XML
  • Enterprise Release 4.7

  • SAP Training Institutes

  • SAP Training Institutes
  • Job Consultants Address
  • SAP Companies Address

  • Business Process Cycle

  • Analyze
  • Design
  • Implement
  • Operate
  • Optimize
  • Skills And Education

  • Logistics Module

  • Sales and Distribution
  • Quality Management
  • Materail Management
  • Plant Maintenance
  • Financial Modules (FI/CO)
  • Project system
  • Production Planning
  • Service Management

  • SAP NetWeaver

  • Introduction
  • Object Model
  • Interoperability
  • Creating Web Apps
  • Java Connector
  • Advantages & Conclusion
  • Life Cycle Management
  • Composite Application Framework

  • SAP Tools

  • SQL Trace Tool
  • SAP BW

  • SAP Modules

  • SAP FI Module
  • SAP CO Module

  • SAP Technical

  • SAP ITS Architecture
  • Financial Management
  • Manufacturing Planning and Execution
  • Customer Order Management
  • Lackbox Processing
  • SD and Financial Accounting Integration
  • SAP - HR (Human Resource)

  • SAP Miscellanous

  • Web Application Server(WAS)
  • Data Archiving
  • Mobile Engine
  • SAP Script
  • SAP Transactions
  • SAP Business Warehouse(BW)

  • SAP Reference

  • SAP Facts
  • SAP Tables
  • SAP Function
  • SAP Report
  • SAP Landscape

  • SAP Others

  • SAP Treasury
  • SAP Finance
  • SAP Data Archiving
  • SAP Exchange
  • SAP Applications Components
  • SAP Software
  • Dunning
  • SAP Payroll Basics
  • SAP BASIS and Security Authorization
  • SAP Backup
  • SAP Router

  • ABAP Tutorials

  • Introduction
  • ABAP Transaction
  • ABAP Function
  • ABAP File Processing
  • ABAP Objects
  • ABAP Syntax
  • ABAP Queries
  • SAPMail Using ABAP
  • ABAP Programming Hints

  • SAP Projects & Codes

  • Finding the user-exits
  • Purchase Order Display
  • Batch Input
  • Dynamic Open SQL
  • Creating Extract Dataset
  • Reading database tables
  • Load table from a UNIX file
  • Create subscreen

  • SAP Resources

  • SAP Books
  • SAP Links

  • Interview Question

  • Common Interview Que.
  • ABAP Interview Que.
  • ERP Interview Que.
  • HR Interview Que.
  • MM Interview Que.
  • PP Interview Que.
  • ALE Interview Que.
  • EDI Interview Que.
  • Basis Interview Questions
  • SAP-SD Interview Questions
  • FI&CO Interview Questions
  • BW Interview Questions
  • CRM Interview Questions
  • Interview Questions

  • Careers at SAP

  • Careers in SAP (SAP Jobs)
  • Advertise