Order management[rev]
- Functions
- Delivery Times/Commitment Dates in Sales Orders
- Alternative Items
- Text control ( maintain, copy, set default and display texts for application objects )
- Order Probability
- Additional information
- 1574381 - FAQ: Collective orders
- 1862445 - FAQ: Production order header
- 1862362 - FAQ: Planned order conversion
- 2392293 - FAQ: Status in the order
- 2261311 - Function module for reading multiple SAPscript texts
- Multiple Address Handling in Order-to-Cash Documents Using SAP Business Partner (s2021, 05.11.2021)
Alternative Items
Text control ( maintain, copy, set default and display texts for application objects )
Transaction VOTXN.
Create a Text procedure, create a Text ID, create an access sequence to search for a text. assign Text IDs and the sequence to the Text procedure, assign the Text procedure to the application object:
Sales document ( header, item ) Delivery ( header, item ), Billing ( header, item ), Shipment ( header ), Financial document , Info record, Customer ( SD, general ).
For the access sequence we can use the application object or a Text (SDVD) with variables like /Z/AG_HEADER_TEXT_&VKORG&_&AUART&. For that we need to a add a data transfer routine and probably a requirement routing ( for exclusion ):
IF XTTXVR-TDNAME CS '&VKORG&'. referenz-tdid = xttxvr-ID_VON.- referenz-tdobject = xttxvr-obj_von.
- referenz-tdname = xttxvr-tdname.
- replace '&VKORG&' in referenz-tdname with FTVCOM-VKORG.
- replace '&AUART&' in referenz-tdname with FTVCOM-AUART.
We can set if the text might be overwritten.
Order Probability
When you create a sales query, you may want to know: What is the probability that the customer will buy from me? The system calculates the probability from master data that can be defined for the sales document type and for specific customers. The estimate is expressed as a percentage. Based on the resulting probability, the system calculates an expected order value and displays it in the top section of the double-line entry overview screen. You can then generate a list of quotations or inquiries in such a way that sales queries with the highest probability of being confirmed are listed first. The following figure shows how the system calculates order probability from master data.
You can configure possible delivery times in Customizing by going to Sales and Distribution Sales Sales Documents Define agreed delivery times.
When you create a sales order with reference to a contract or quotation the system copies the delivery time into the sales order item. If you do not enter a delivery, nothing changes in sales processing.
The commitment date is calculated using the delivery time in contract releases with a delivery time, or in sales orders that refer to a quotation with a delivery time. The committed quantity is calculated from the agreed delivery time or from the confirmed quantity, according to the settings you made in Customizing. If you change the material, quantity, delivery date or delivery time in the sales order, the system recalculates the committed quantity.
Answer: Status management compares the system status at the time of saving with the system status at the time of import. If there is no difference, no status change document is updated. For example, no status change document is created for the status REL (released) if a released order is changed, the master data is read subsequently (which resets the status to "Open"), and the order is released again before you save.
This activity has been enhanced with address determination attributes. For more information, see the documentation of the activity in Customizing under Sales and Distribution Partner Determination.Delivery Times/Commitment Dates in Sales Orders
You can enter a delivery time in contracts and quotations.
- In the contract , the delivery time fixes the time period that the customer has given the vendor between contract release and delivery receipt.
- In quotations , the delivery times enables you to agree on a guaranteed maximum delivery time once the order has been entered.
- In the sales order , a committed quantity and date are issued alongside the confirmed quantity calculated by the availability check, which enables you to see whether committed quantities and delivery dates have been complied with.
These new functions are particularly useful if you are working with contracts and are expecting bottlenecks and where obligatory agreements on dates have to be met. Above all, they are suitable for the high tech and chemical industries as well as those branches of industry with customer make-to-order production.
You can configure how the commitment dates are calculated in Customizing for the sales document type in the Commitment date field. You can choose one of the following rules:
A: Consider agreed delivery time only
Here, all the required schedule lines are committed for the date that follows the delivery time at the distance agreed on when you entered the sales order. If the customer requires a later date, this date is confirmed. The commitment situation does not influence the calculations and if you don’t specify a delivery time, the system does not calculate any committed quantities.
B: Calculation after the first confirmation date
The committed quantity is calculated from the first commitment situation. If a delivery time is available for the item, the system takes it into account in calculation rule A and the system commits the quantity for the earlier date. If you change the material, quantity, delivery date or delivery time in the sales order, the system recalculates the committed quantity. In each case the current commitment situation is valid when you save the document.
C: Calculation after the first confirmation date
If you enter new items, rule C corresponds to rule B. If you save the document again and the customer’s commitment situation has improved, the system saves the better situation as the committed one. As in calculation rule B, the system recalculates the commitment dates if you change the material, quantity, requested delivery date or delivery time.
No entry: The system does not calculate or display commitment dates.
-
Delayed Sales Order Indicator
There is a status field for the sales order header and items that specifies whether the availability check has covered the commitment for undelivered order quantities. If you choose matchcode M, you can display all sales documents that have the "delayed" status. A delayed sales order is one where the committed quantities could not be either completely or partially committed, or where the quantity will be not be confirmed as committed until a later date.
Additional information
1862362 - FAQ: Planned order conversion
Solution
Question:
You navigate to the stock/requirements list from the collective conversion of planned orders to production orders (transaction CO41) or to process orders (transaction COR8). After you return to the collective conversion, you notice the following symptoms:
* Sorting that was previously applied is no longer taken into account.
* Planned orders that were selected before you navigated away are no longer selected.
* Changes made in the overview have been undone.
* Manually removed planned orders reappear.
Answer:
The system behavior is correct. When you return to collective processing, the system reselects the planned orders according to the original selection criteria. This is because planned orders can be changed using the stock/requirements list and these changes would otherwise be ignored. This system design was introduced with SAP Note 1901579.
Question:
In which cases does the system reread the master data (BOM) during planned order conversion?
Answer:
The Customizing for the order type parameters includes a "BOM Explosion" field on the "Planning" tab page. If this field contains an entry, the BOM is exploded again during planned order conversion. The explosion date can be controlled using the value in the field. If the field has the value 1, the explosion date from the planned order is used. If the value is 2, the explosion date is redetermined. This relates to transaction OLP8 (for production orders) or COR4 (for process orders).
In mass processing (COHV or COHVPI), you can use the "Reread BOM" function parameter to control the automatic reading of the BOM.
When planned orders are converted to production orders, the system also rereads the BOM if the order is subject to order change management (OCM). This applies if the material master of the finished product contains an overall profile for order change management. This profile can be found in the "Work Scheduling" view.
Question:
Can a partial planned order conversion be performed using mass processing or collective conversion?
Answer:
No, this option does not exist. For a partial conversion, use the corresponding transactions for individual processing. Another option is the stock/requirements list (transaction MD04).
1574381 - FAQ: Collective orders
This SAP Note provides answers to frequently asked questions (FAQs) about collective orders.
1. Question: Why is it not possible to use different order types for the leading order and the subordinate orders?
Answer: This behavior corresponds to the SAP standard system. The order type of the leading order is passed on to all subordinate orders. This is because the order type or the order-type-dependent parameters control the bill of material explosion or the goods movements in the collective order, for example.
2. Question: When the parent order is released, the subordinate orders are not released. Why?
Answer: The automatic release is controlled via the production scheduling profile. This is copied from the material master for the header material of the particular order. Check whether a relevant profile is assigned to the subordinate orders.
3. Question: Even though automatic release is set in the production scheduling profile, the subordinate orders are not released if the release has been rejected in the leading order.
Answer: This is not an error. If the release is canceled in the leading order, the subordinate orders are not automatically released. As a workaround, you should be able to use the mass release in transaction COHV or CO05N.
4. Question: The settlement rules in the collective order are not clear.
Answer:
A. Settlement rules when the "Coll.order with Goods Movement" indicator is set
The settlement of the orders is the same as for non-dependent orders (generally to the material).
Settlement rules when the "Coll.order with Goods Movement" indicator is not set
The subordinate orders settle to the superior order, and in this case, they have a settlement rule for AUFNR.
The leading order can settle to its header material, an assigned sales order or a WBS element.
5. Question: Can I set the "Coll.order with Goods Movement" indicator for an order at a later point in time?
Answer: For existing orders, a change is not possible in the standard system. This is because the indicator affects not only the goods movements, but also the settlement rule.
6. Question: Scheduling for the collective orders is not clear.
Answer: See SAP Notes 151503 and 150007.
7. Question: Why is a new order number assigned in the collective order when the master data is read?
Answer: See the explanations in SAP Note 440585.
8. Question: When an order is closed or deleted in the collective order, the system issues error C2 305 "Order &1 is assigned to account of order &2".
Answer: To close order 2, it is sufficient for order 1 also to be closed or the deletion indicator set. However, if you want to delete order 2 (you set the deletion indicator), it is not sufficient to close order 1 and set the deletion indicator; the deletion indicator must already be set for order 1. For information about this, see SAP Note 983490.
9. Question: As of Release ECC 5. 00, you can no longer use the profile defined in the parameters dependent on the order type (OPL8) to influence the collective order overview. Why?
Answer: As of Release ECC 5.00, the collective order overview uses the new SAP List Viewer (ALV). This is controlled using layouts instead of profiles. You can define and save relevant layouts in the collective order overview.
10. Question: As of Release ECC 5. 00, an error occurs when you use batch input for the collective order overview. Why?
Answer: As of Release ECC 5.00, the collective order overview uses the new ALV, which does not support batch input. SAP Note 1313398 provides a modification. If you implement this, the collective order overview is displayed in the old representation without ALV. This modification enables you to continue using batch input.
11. Question: Why is the "Environment / Confirmation / Enter" menu option for collective orders active only in transaction CO03 and always grayed out for normal orders?
Answer: The menu option for navigating to the confirmation from the order processing transaction is always grayed out for normal production orders; that is the standard SAP behavior and is not an error. SAP does not plan to release this function for normal production orders.
For collective production orders, the menu is activated when the production order is displayed (transaction CO03). Transaction CO02 sets a lock on the order. As a result, no confirmation can be entered. Therefore, SAP Note 376548 has prevented this navigation.
12. Question: When reading the master data of a subordinate order, some of the higher-level orders are also assigned the status CRTD, even though no master data is read. Why?
Answer:
Status FREI indicates a release for production. If a subordinate order loses the status FREI, the higher-level order must also lose the status FREI. If the lower-level order cannot be produced, the higher-level order also cannot be produced.
13. Question: For a collective order with an order type for which the "Coll.Order with Goods Movements" indicator is NOT set, the system updates the goods receipt quantity / goods issue quantity during the confirmation. Why?
Answer:
The system behavior is correct. The "Coll.Order with Goods Movements" indicator results in the creation of actual material documents for these automatic postings. If the indicator is not set, the system updates the quantities after the posting without a material document being created.
14. Question: Do newly added operations influence the logic of automatic goods movements in the collective order?
Answer:
If the last confirmable operation of a subordinate order is partially or finally confirmed, this is now noted by setting the internal status I0361 for the corresponding operation.
If, after a confirmation, additional operations are added to the last confirmable operation, no dependent goods movements occur when you confirm the "new" last confirmable operation. These are carried out only when you enter the original last confirmable operation.
This logic was implemented with SAP Note 553692.
15. Question: Are there restrictions when using serial numbers in the collective order?
Answer:
Yes, it is not possible to create serial numbers in subordinate orders of a collective order in the R/3 standard system. This is correct and not an error.
SAP Note 391606 provides a modification that partially removes this restriction.
Other Terms
FAQ, collective orders, order type, order-type-dependent parameters, BOM, BOM explosion, bill of material, goods movements, header material, automatic release, COHV, CO05n, collective order with automatic goods movements, WBS element, scheduling collective order, C2 305, C2305, OPL8, I0361, serial numbers in collective order, dependent goods movements.
1862445 - FAQ: Production order header
This SAP Note provides answers to frequently asked questions (FAQs) about the order header.
Question: Why is the field for the sales order schedule line not filled for many orders?
Answer:
Since SAP Note 459288, the "Sales order schedule" field (AFPOD-KDEIN) is only still transferred for assembly orders.
Question: A WBS element is assigned to the order, but the field PSPEL in the table AUFK is initial. Why?
Answer:
The WBS element is saved in field PROJN in table AFPO.
Question: When I create a production order with reference in CO01, the WBS element from the reference order is not also transferred. Why?
Answer:
Transaction CO01 is not designed to do this, use transaction CO10 instead.
Question: When is the status GLFT set for the order header?
Answer:
Read consulting Note 1857198.
Question: Why is the "Environment / Confirmation / Enter" menu option for collective orders active only in transaction CO03 and always grayed out for normal orders?
Answer:
The menu option for navigating to the confirmation from the order processing transaction is always grayed out for normal production orders; this is the standard SAP behavior. This is not an error. SAP does not plan to release this function for normal production orders.
For collective production orders, the menu is activated when the production order is displayed (transaction CO03). Transaction CO02 sets a lock on the order. As a result, no confirmation can be entered. Therefore, SAP Note 376548 has prevented this navigation.
Question: When I create a production order with reference in transaction CO01, the settlement rule is not copied. Why?
Answer:
For an explanation why this is the case, refer to SAP Note 82737. To copy the settlement rule, use the "Select order objects" button (in transaction CO01, this is the button after the reference order field) to set the "Settlement Rule" flag. To make this the default setting, implement modification note 400400.
Question: When the quantity is changed in the order header, is the assembly scrap from the material master read again and used to calculate the scrap?
Answer:
No, the system performs a proportional calculation here and rounds up when necessary.
Example: There is an order quantity of 2000 pieces, of which 10 pieces are scrap (0.5%).
If the quantity is now changed to 3300 pieces, the new scrap is calculated as follows: 3300 * 10 / 2000 = 16,5 = 17 pieces (rounded up)
Thus the order quantity is now 3300 pieces, and 17 of them are scrap.
If the quantity is changed again to 3000 pieces, the new scrap is calculated as follows: 3000 * 17 / 3300 = 15.45 pieces = 16 pieces (rounded up)
Question: The system assigns order numbers incompletely. How can I get the system to assign order numbers completely?
Answer:
Refer to SAP Note 456777.
Question: Which time zones are used in the order?
Answer:
The dates in the order on the "General" tab page are displayed in the time zone of the plant. An exception to this is the field "Reported finish" (actual finish date): Here, the posting date from the material document is displayed for the goods receipt.
The data on the tab page "Administration" is displayed in the system time.
The dates of the status change documents are explained in detail in SAP Note 1236560.
Question: Since the conversion to SAP S/4 HANA, the system requests a production version in the order. Why?
Answer:
This behavior corresponds to the standard system; the production version is absolutely necessary in SAP S/4 HANA. More information about this is available at help.sap.com.
Question: How can I create an order without a bill of material in SAP S/4 HANA?
Answer:
If a bill of material has not been assigned to the production version, the system tries to explode a bill of material using the settings in order-type-dependent Customizing (OPL8). Therefore, if you do not want an order to have any components, you should create a bill of material without components and use it in the production version.
2392293 - FAQ: Status in the order
in Customizing of the parameters for the order type (transaction OPL8 or COR4), in the view "Implementation", the creation of status change documents is activated. Despite this, not all of the status changes are logged.Answer: Status management compares the system status at the time of saving with the system status at the time of import. If there is no difference, no status change document is updated. For example, no status change document is created for the status REL (released) if a released order is changed, the master data is read subsequently (which resets the status to "Open"), and the order is released again before you save.
2261311 - Function module for reading multiple SAPscript texts
Function module READ_MULTIPLE_TEXTS:
Used to select texts to be read via wildcards or ranges tables
Input parameter:
CLIENT: Text client
NAME: Text name
OBJECT: Text object
ID: Text ID
LANGUAGE: Text language
Wildcards such as '*' can be used for all parameters.
NAME_RANGES: Ranges table for the text name
OBJECT_RANGES: Ranges table for the text object
ID_RANGES: Ranges table for the text ID
LANGUAGE_RANGES: Ranges table for the text language
You can use, for example, 'TYPE RANGE OF' to define a ranges table. It is also generated via the SELECT-OPTIONS command.
If, for example, the NAME and NAME_RANGES fields are filled for the text name, the system uses the entries in the ranges table.
ARCHIVE_HANDLE: Archive handle; if set, all texts are read from the archive.
LOCAL_CAT: Use of the local catalog; The texts are not stored in the memory beyond the limitations of the internal session.
WILDCARD_PLUS: A '+' in the text name is a wildcard and not part of the name.
These parameters are explained in greater detail in the function module documentation for the SELECT_TEXT function module.
Function module READ_TEXT_TABLE: Used to select texts to be read via an internal table
Multiple Address Handling in Order-to-Cash Documents Using SAP Business Partner (s2021, 05.11.2021)
Have you ever wondered why SAP S/4HANA’s Business Partner (BP) allows to maintain multiple addresses, but Order-to-Cash documents can only use the customer’s standard address? Have you ever wondered why you need to maintain multiple BPs just because your customer has asked you to deliver your goods to different addresses?The reason for both is that the standard customer master data model in Sales and Distribution can only store one single address per customer master record. Therefore, if you had to deliver your goods to a different address for a certain customer, you had to maintain a new customer master record with a ship-to party address and to assign this ship-to party to the customer master sales data using the corresponding partner function.
- In the Define Address Types activity under Cross-Application Components SAP Business Partner Business Partner Basic Settings Address Determination
- In the Assign Transaction to Address Type activity under Cross-Application Components SAP Business Partner Business Partner Basic Settings Address Determination
- In the Set Up Partner Determination activity under Sales and Distribution Basic Functions Partner Determination
- For ship-to party: all addresses that can be used for sending goods
- For bill-to party: all addresses that can be used for sending bills (that is, billing documents)
Comments
Post a Comment