Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
QI (Package) QM IMG and area menu
IMG Activity
| ID | OLQS_BS | Define Status of Supply Relationships |
| Transaction Code | S_ALR_87004738 | IMG Activity: OLQS_BS |
| Created on | 19981222 | |
| Customizing Attributes | OLQS_BS | Define status of supply relationships |
| Customizing Activity | OLQS_BS | Define status of supply relationships |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OLQS_BS |
In this step, you define status profiles for the supply relationships and assign an inspection type to the statuses in the profile.
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.
Activities
- 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.
For a detailed description of the general status management function,
refer to the chapter Basic Settings and Environment, Central Functions, status profile.
- If necessary, assign an inspection type (which indirectly assigns a task list usage) to the statuses in the profiles.
- 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.
Further notes
Tracking 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. 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".
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OLQS_BS | 0 | HLA0001806 | QM Control in Procurement |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| BSVS | L - Logical transport object | BS02 | OLQS | Maintain status profiles | ||
| V_TQ32A | V - View | SM30 | 9999999999 | Assign delivery status for inspection type |
History
| Last changed by/on | SAP | 19990312 |
| SAP Release Created in |
