Capable To Confirm - help.sap.com

PUBLIC2021-03-16

Capable To Confirm

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Capable to Confirm (CTC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2 CTC Process when Creating a New Sales Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 Process Overview in Flowchart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42.2 Process Description: Creating a Sales Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 CTC Application Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 CTC Logic in Detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

5 Functional Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6 CTC Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2 PUBLICCapable To Confirm

Content

1 Capable to Confirm (CTC)

Availability Check and Order Creation

The consulting solution CTC – Capable To Confirm is an extension of the ATP check during the creation of sales orders.

When sales orders are created (transaction VA01), the availability of a material on the desired confirmation date is checked. This is done in the standard system using the ATP check.

If there is not enough material in stock, the ATP check determines a missing quantity that cannot be confirmed for a confirmation date.

In the standard system, this incorrect quantity would be reported to the user, assuming corresponding customizing has been configured.

The CTC check begins at this point.

If an missing quantity occurs in the ATP check, the ATP check forwards this missing quantity to the CTC check.

In the CTC check, the system tries to create a manufacturing order for this missing quantity in the form of a planned order. This causes material to be produced to cover the missing quantity in time. In the process, the system checks for free capacities for producing the material and for component availability.

The availability of the components of the material determines the earliest point in time at which a material can be produced. Therefore, the component availability is checked before the search for remaining available capacities is begun.

The check for free capacities compares the free capacities on the machines with the orders already dispatched there.

The check for free capacities can also take the specifications of the LMPC timetable into account.

The LMPC timetable can be used to define the days when a material can be produced and the periods in which they are located. The LMPC timetable is an additional restriction placed on the available capacities.

The LMPC timetable is optional. LMPC is a separate consulting solution. The check with the LMPC timetable can be performed only if LMPC exists in the system.

If all checks are positive, a planned order for producing the material is created and dispatched. The new quantity is confirmed.

If the missing quantity cannot be produced on the desired date, the newly created order is scheduled for the next available capacity. This creates an alternative date for the material availability. The user can accept it or reject it.

Related Information

Capable to Confirm (CTC) [page 3]

Capable To ConfirmCapable to Confirm (CTC) PUBLIC 3

2 CTC Process when Creating a New Sales Order

This section provides an overview of using CTC when you create a sales order.

2.1 Process Overview in Flowchart

Process CTC

The CTC check takes place as part of the standard product availability check (ATP) that is executed during sales order entry.

Here you can see an overview of the steps in general. The purple fields indicate the steps in CTC .

Process Overview: Creating a New Sales Order with CTC

2.2 Process Description: Creating a Sales Order

Creating a sales order with CTC

Initially, you can see the capacity usage for 5 machines in the graphic of the LMPC HJPT planning board.

An order with 3 operations is dispatched on machines 1 and 2.


CTC Process when Creating a New Sales Order

Capacity Situation at the Beginning

TipTo better depict the process, this overview has been added to the LMPC HJPT planning board. Like CTC , the HJPT planning board is a consulting solution and not part of the SAP standard system. It can be obtained separately.

Now use transaction VA01 to create a standard order.

Creating a Standard Order

Maintain an item for a material that is checked with CTC.

Capable To ConfirmCTC Process when Creating a New Sales Order PUBLIC 5

Order Creation

If you press the Return key, the product availability check begins.

First, the available quantity is checked according to standard ATP logic.

CautionIf a check against the replenishment lead time (RLT) is active in the standard ATP check logic of the ATP check, the system does not perform the CTC check because the standard ATP against the replenishment lead time gives a complete confirmation. Therefore no remaining requirement is created from the ATP check. The check against replenishment lead time must not be activated for the CTC scenario.

If an unconfirmed partial quantity or a remaining requirement remains during the ATP check, the system triggers the CTC check.

The CTC check is executed only if the following checks are positive:

● CTC is active for this material.● The operation is a sales order.● The operation does not come from a rescheduling.● There is only one demand. The item contains only one requirement item. Several requirement items per

item are not allowed.

In this example, the requested quantity cannot be confirmed from the warehouse for the date/time.

The CTC check starts.

The following steps are executed:

● A simulative planned order is created in the background for the remaining quantity of the material.● The availability of the components of this planned order is checked.● A capacity check takes place for the capacity requirements of this order. A time of dispatch is determined.

If the CTC check was able to confirm the remaining requirement on the desired date, only a message is displayed in the status bar.

It shows the quantity of the created planned order and the date on which the quantity of the planned order was confirmed.



Example Confirmation

If the quantity could be confirmed using the CTC check, but not on the desired date, only later, a dialog box appears. The logic asks the user whether the delayed date should be applied.

The following groups of information are displayed:

● The original demand with date and quantity● The confirmations from the standard ATP with date and quantity (if available)● The confirmation from the CTC check (if available)

Dialog Box: ATP and CTC Confirmation Dates

In the example, the requested delivery date is 02/05/2020. The requested quantity is 47 pieces.

The material staging for the 47 pieces is to take place on 02/03/2020.

The SAP standard ATP can confirm the material staging of 8 pieces for 02/10/2020. This is the order quantity of the order that was dispatched on 02/08/2020 (see screenshot of LMPC HJPT planning board above).

The CTC check can confirm the staging of the remaining quantity of 39 pieces on 02/12/2020. A simulative planned order has been generated for this purpose, and a check for available capacity has been carried out. The planned order has been neither dispatched nor saved yet.

NoteIn the background (for example, BAPI or IDoc) the system always applies the scheduling result of the CTC, regardless of whether it is on time or late.

The user can now choose from among 3 functions:

● Display CTC application log● Discard CTC check result● Apply CTC check result

Calling the Application Log of the CTC Check

The log can be used to trace how the result came to be.


CTC Check Log

From the log, you can see that an order for the component material could not be created until 02/10/2020 due to a lack of material availability.

The confirmation date of the material availability is 02/12/2020.

Discarding the CTC Proposal

If the proposal is rejected, the process continues with the standard screen of the availability control. The CTC quantity is not applied. In this case, the newly generated simulative CTC planned order is deleted again.

The system continues with the standard ATP logic.



The system branches to the standard ATP results screen.

Results Screen when Discarding

Applying the CTC Proposal

If the CTC proposal is accepted, the confirmed dates and quantities are transferred from the CTC check to the ATP check in the background.

Afterwards, the system proceeds with the availability control. However, the screen is not ready for input yet. The proposal must be applied as it was generated.


Availability Control not Ready for Input

Since the user had already confirmed that the result should be applied, the planned order for the CTC is received. Therefore, the confirmation situation can only be revised to a limited extent at this point.

The quantity fields are no longer ready for input, and the “one-time Delivery” has been removed from the header and deactivated in the list.

The user can now only choose between the options for delivery proposal and full delivery. Both have no effect on the CTC planned orders.

It is recommended that you choose "Delivery Proposal", since in this case, the system generates one schedule line for each available quantity in the order item.

After making a selection, the user returns to the overview for creating the standard order.

If the user is no longer satisfied with the decision, they can trigger a new ATP check manually. Alternatively, they can also delete the item in the sales order.

They can now enter another item for the next material.

The system simulates storing all planned orders that were created for the individual material items in the memory.

When you store the new sales order, the planned orders are scheduled, dispatched, and saved for the calculated dates. They are written to the database only when you save.

If you look at the planning situation in the graphic of the LMPC HJPT planning board after saving, you can see the newly created planned order that was created and dispatched for 02/10/2020.



Result After Saving

CautionIf the user calls the ATP quantities screen after the CTC check, the quantity of the order created with CTC is not displayed there. Since this order is still in simulation mode and is not posted to the database, its quantity is not included in the calculation.

Termination If Errors Occur During the CTC Check

If an error occurs during the CTC check, the system displays a dialog box informing the user about the error.

Information about the Error in the CTC Check

The dialog box makes it possible to jump to the CTC application log.

The details about the error can be read in the application log of the CTC check.

Errors can be caused by the following:

● The requested material is locked at the same time by another user. No additional CTC checks are possible for this material until the other user has saved their new sales order and thus released the locks on the material. The user name of the locking user is displayed in the log.

● A component of the requested material is locked simultaneously by another user.● A component of the material is not available during the check period.● CTC does not find sufficient capacity in the specified time horizon to dispatch the planned order.

Example Errors in the Application Log


3 CTC Application Log

Application log for the CTC check

Whenever a CTC check is performed, an application log is created.

Since the CTC check is executed for each item in a sales order, a CTC application log can exist for each item in a sales order.

The application logs are saved only if the sales order is saved.

It is possible to view the CTC application log from within transaction VA01 only if the requested date cannot be complied with or if an error occurs. If the requested date is feasible, the log is not displayed.

However, it is possible to call up the created log using transaction SLG1.

Object: /SAPLOM/CTC

Subobject: /SAPLOM/C/C_CP.

Each log is available for 30 days. Afterwards, it is deleted automatically by the system.


CTC Application Log

4 CTC Logic in Detail

Detailed description of the CTC logic

This unit describes the individual steps of the CTC logic in detail.

The CTC check is called if the ATP logic determines a missing quantity for the requested date when an item is created in a sales order.

The CTC check receives the following as input: the item number of the order, the material number, the requested quantity, and the requested staging date.

The application log is generated for this item.

A lock is set for this material. The lock is necessary so multiple users do not request the same material at once and commit the available capacities twice.

The lock remains until the sales order is posted or until the item is discarded from the sales order.

If the material is already locked by another user, the CTC check terminates.

The CTC check uses its own lock table. Therefore, no interaction with other applications can occur.

It is read from the CTC customizing for the check period and converted into concrete date values.

A simulative planned order for the order material in the scope of the missing quantity is created so that production ends on the requested material staging date.

There is a BOM explosion and component quantity determination for the planned order. The components are then checked. Text items are removed from the set of components. The same applies to phantom BOM items and items with zero quantities. Zero quantities can arise if alternative BOM items exist.

An availability check is carried out for the components of the planned order.

The availability of the components determines the earliest production date for the order. It restricts the search area for the search for free capacities.

Locks are also set for the components of an order. In an SAP GUI, a user can request various materials that use the same components.

If this happens, the quantities are simply added for each component for all orders for the availability check. That makes it possible to correctly determine the availability for a material.

However, the check terminates if the components are locked by another user in another SAP GUI.

The check period is adjusted after the availability check.

The available capacity is now determined.

The available capacity is determined for all the capacities on which the operations of the order are supposed to be produced. The available capacity is calculated for the entire check period.

When the available capacity is calculated, only the operations dispatched for the capacities are considered as committed capacity. Orders that are scheduled at certain times but that are not dispatched are ignored.

Capable To ConfirmCTC Logic in Detail PUBLIC 13

If LMPC exists as a consulting solution in the system, the available capacity can be calculated using the LMPC timetable. This can be activated via CTC customizing. The LMPC timetable can be used only for plants that have an LMPC license. The logic then reduces the available capacity that was previously calculated and leaves only the planning windows that have been specified by the LMPC timetable open.

CautionIf a material is produced at different work centers, a timetable must be maintained for each of these work centers when the LMPC timetable is used. If no timetable exists for one of the work centers, the available capacity for this work center is set to zero. This would cause the check to terminate without a result.

In the next step, the search for free capacity takes place in order to place the simulative planned order in the work center.

The capacity check takes place for all the operations of an order for the capacity relevant to scheduling.

Only one capacity can be relevant to scheduling at any given time. For example, if a work center has machine capacity and labor capacity and the machine capacity is relevant to scheduling, only the machine capacity is checked.

The capacity check always begins on the scheduled date of the planned order.

A planned order is supposed to produce the quantity for the requested date on time – not later and not earlier.

If the check for the requested date fails, the logic switches to search backwards in time. This happens because it is better to produce an order too early than too late.

The system searches backwards in time for free capacity until the left end of the check period that was predefined via CTC customizing has been reached.

If no suitable period for the dispatch is found during the backwards search, the logic switches to search forwards beyond the desired delivery date. The system searches forwards for a free date until the right end of the check period has been reached.

If no free capacity could be determined, the CTC check terminates. An error is reported to the user.

If the check finds a suitable period for the order, the new start date is saved internally, and the available material staging date is confirmed. The available date is calculated in a similar manner as when the SAP standard is used; the factory calendar and goods staging time are taken into account.

The planned order internally fills the available capacity at the calculated point.

The capacity commitment of the simulative planned order is retained internally and is also taken into account if the same user requests another material that is produced on the same machine.

CautionThis capacity information is available for the same user, but not for another user who simultaneously requests other materials that are also produced on the same machine. This can lead to an overbooking of the capacities.

The capacity information is encapsulated per GUI and is not available system-wide.

The simulative planned order is not yet updated in the database.

If the user does not accept the result of the CTC check and rejects the item,

the planned order is deleted.


CTC Logic in Detail

Only when the sales order is saved in VA01 are the planned orders posted for the individual items on the calculated date.

For this purpose, the orders are set to the calculated dates. If immediate dispatch is not deactivated in CTC customizing, a status object is generated, and the status dispatched is set. The planned order is then dispatched.

Capable To ConfirmCTC Logic in Detail PUBLIC 15

5 Functional Constraints

Limits of Applicability of CTC

CTC is a consulting solution. It was developed as part of an enhancement project in cooperation with customers.

The consulting solution was developed for the customer’s specific application cases. Therefore, the scope of functions is limited and does not correspond to the scope of functions of an SAP standard solution.

The standard SAP functionality used is documented only if it is required for the process flow of the scenario. Additional standard SAP functionality is not part of this documentation.

All scenarios that are not described in this documentation are not supported by CTC.

It is possible that an scenario that is not described may work with CTC. If you want to test a scenario like this, CTC consulting can assist you.

If you have a special requirement that is not yet supported by CTC, you can commission CTC development to develop a new function for a scenario. For functions that might also be of interest to other users, a CO innovation with reduced effort is possible.

CTC is constantly being further developed. If you do not have budget for a new development, you can use SCM consulting solutions’ “Idea Place” to submit proposals for functions.

CTC development welcomes your proposals and will check them. Suggestions directly from the user of the solution are very helpful. These suggestions can be implemented in future CTC versions. However, there is no guarantee that submitted proposals will be implemented.

CTC has the following functional limitations:

● PP planned orders and PP-PI planned orders are possible as generated planned orders. Other planned orders are not possible.

● When the sales order is created, the items must be entered individually, and the ATP check must be triggered with a return. It is not possible to enter multiple items at the same time. The CTC check would be executed only on the first item entered each time.

● The CTC check runs only at the level of the material and its components. A multilevel check across additional low-level codes is not possible.

● The function is performed only for an SD ATP check (not an MM or PP component check)● The function is not run in rescheduling.● The function is performed only for sales order requirements (sales orders VBTYP = ‘C’ or free-of-charge

sales orders VBTYP = ‘I’).● CTC is not run if there are multiple requirement items in an item. Requirement items are not supported.

There is exactly one requirement item for each sales order item.● It is assumed that all components for the orders must always be available at the start of the order. The fact

that components can be included only in later operations of an order is not taken into account.● CTC always uses the earliest location to calculate the capacity check. It is not possible to dispatch for the

latest dates.● The capacity check considers only dispatched orders as occupancy for a capacity. Orders that are not

dispatched do not reserve capacity.


Functional Constraints

● In the capacity check, it is assumed that all operations for an order are processed consecutively. Routings with parallel operations lead to incorrect results. Suboperations are not supported, either.

● The capacity check checks only for free capacity. Existing capacity assignments are not moved.● Only the capacity relevant to scheduling is checked during the capacity check.● It is not possible to perform parallel requests for the same material. Only one user can check a specific

material with CTC. If there is a conflict , CTC terminates with an error message.● It is also not possible to check the same material in different items more than once within a sales order. A

header material can be used by only one user and for only one item per sales order.● It is not possible to make parallel requests from different users for the same components. If there is a

conflict , CTC terminates with an error message.● The planned order created for the material is always created with the complete missing quantity. It is not

possible to split a large missing quantity into several orders.● The capacity commitment of an order is visible only once the order has been posted. This means that if two

users are requesting two materials in parallel and they are produced on the same machine, the available capacity may be overbooked.

● CTC supports only scheduling types 1 “Forward”, 2 “Backwards”, and 3 “Only capacity requirements”.● If the LMPC timetable is used, only logic 2 of the LMPC timetable is supported.● After the planned order created by CTC check has been saved, there is no connection between the sales

order and the created planned order. Rescheduling planned orders can cause other sales orders to consume the quantity of the created planned order.

CautionThere is a material determination function in SD. This is a logic for replacing a material with an equivalent material. This can be defined so that it can be executed according to ATP logic. This check would run multiple ATP checks at the same time to find the best material with the highest availability. This setting must not be used with CTC because parallel ATP checks are not intended.

Capable To ConfirmFunctional Constraints PUBLIC 17

6 CTC Support

CTC Support for Errors

If you want to report errors for the CTC consulting solution, you can do so via the SAP ticket system.

1. Create an OSS incident under the component XX-PROJ-CON-CTC. For the priority of tickets, refer to SAP Note 67739 .

2. Make sure that the system connection is open and that credentials for logging on to the system are provided in the secure area of the incident. Also check that the provided user name has authorization for the transactions VA01, VA02, and VA0, and for debugging in the system.

3. Describe the issue: What is the system behavior and what would you have expected?4. Provide a step-by-step description with an example of how to reproduce the error. An example includes the

system name, client, and data for creating a sales order. You can describe the example in a document and attach it to the ticket.


CTC Support

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/67739

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Capable To ConfirmImportant Disclaimers and Legal Information PUBLIC 19

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Documents

Capable To Confirm - help.sap.com