Configuring Availability check

1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as 

2. Backorder processing, rescheduling and ATP quantities. Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date. 

3. Rescheduling: is a proposal of how – confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority. 

4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) – planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics – sales & distribution – sales – environment – availability overview. 

5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view. 

6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record. 

7. There are three types of availability checks – 

• Check on basis of ATP quantities.

• Check against product allocation.

• Check against planning. 

Configuring Availability check through Checking Groups 

1. The checking group + checking rule determine how the availability check is to be performed. 

2. The checking group determines whether and how the system checks the stock availability and generates requirements for material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements (daily/weekly) or individual requirements for each sales order. 

3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking rule is specified internally within the system and cannot be changed. 

4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be carried out with or without the replenishment lead time. 

5. Briefly explaining the above – checking group determines which type of requirement to be passed on to MRP whether it be individual or summarized and checking rule which is at the transaction level and can be configured independently for each application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check checking group has to work in conjunction with checking rule. 

6. Advantages of individual processing over summarized processing – 

Backorder processing is possible. 

You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and requirements placed on stock. 

The system automatically uses individual requirements in case of special stock items. 

7. Required data for the Availability check to be carried out – 

The Availability check must be switched on at the requirement class level. 

The Availability check must be set at the schedule line level. 

A requirements type must exist by which the requirements class can be found. 

A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in MMR). 

A checking group must be defined in the material master record in the MRP3 screen in the availability check field. 

8. Configuring Availability check and defining Checking Groups – 

Checking groups are introduced into the sales order based on the setting in the material master record. 

SAP standard checking groups are 01 – summarized requirements and 02 – individual requirements or you can create your own by copying the standard ones. 

Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either individually or by day or week. 

Block quantity required can be set if you want several users to be able to process the material simultaneously in different transactions without blocking each other. 

The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check. 

9. Defining material block for other users – the block check box is an indicator that enables you to block material master records of a particular material during the availability check and restrict other users from accessing same master record and reserve the material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material. 

10.Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the material master record. 

However if there is no entry present in the material master record for the checking group, a default value can be set here, depending on material type and plant. 

This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order. 

If an entry exists, this default value is over written by MMR. 

11.Controlling Availability Check – in this section, you tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check in addition to whether or not to consider the replenishment lead time. 

12.These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sales and distribution transaction. 

13.These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to be shipped. 

14.It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage location level. This indicator is used to set the scope of the availability check. 

15.It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the check at plant level only and does not take the storage location into account that is specified in the reservation. 

16.Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to become available. It is only used when doing an ATP check and is taken from MMR. 

17.defining the elements in the availability check entirely depends on the business needs, but a few tips are given under – 

When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is going to come into the plant. 

A shipping notification on the other hand - a confirmed purchase order – is a good indicator of receiving stock on a specified date. 

It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually receive the stock into plant or warehouse for which you are creating a delivery.

On-line Service System or OSS

FAQ on SAP OSS

What is the use of OSS?

In day-to day business customers who are using SAP software encounters problem or bugs with SAP

software. To resolve the issues faced by customers SAP has provided an on-line solution.What? SAP software is having problems or bugs? Yes, any software product is not 100% pool-proof. SAP is continuously updating the versions for better performance and options.

Where can i access SAP OSS?

Log on to www.service.sap.com. Under the SAP Support Portal, click on SAP notes search.

Do i need user ID and password to enter into the OSS?

Yes, you need an User ID and Password to enter into the site. It will be provided by the BASIS Team in the Project. When they create SAP User ID, they will create OSS notes ID also.You can also register individually in the site.

What is OSS Notes number?

After entering into SAP notes search, you can search for the problem using keyword appropriate for your problem. If you have specific OSS notes number with you, then you can directly enter the OSS notes number and you can see the Notes explanation.

How to apply OSS notes number?

Before applying OSS notes number into your SAP system. You need to check whether it is already

implemented in your SAP system or not. If it is not implemented you can go ahead.There are some OSS notes, which we should implement manually, that means we need to change the code in the programs/objects ourselves according to the steps mentioned in the problem.

I did not find any OSS notes appropriate for my problem or bug. What i have to do?

If the OSS notes displayed are not helpful to solve your problem. You can write to SAP Service describing your problem. You problem will be answered by SAP Support team.How to apply OSS notes in my SAP system? What is the T-code and what are the steps. 

Testing mathologies and types in SAP Module

Testing : the core team members along with endusers will test whether the postings done in SAP is resulting as per the requirements of the organisation. They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data. 

Unit testing is refer to the module which are going to implement. SD, MM, FICO etc. there will be test script based on that testing will be performed. 

Integration testing will be cross the modules. MM-SD-FICO for example. Integration testing is also called SIT ( System integration testing) 

Testing methodologies and types: there are 6 types of testings: 

1. Unit Testing
2. System Testing
3. System Integration security Testing
4. Performance Testing
5. User Acceptance testing
6. Regression Testing

Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice. 

Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.

Security testing you will be testing different roles and functionalities and will check and signoff.

Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software.

Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.

User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.

We use different software during testing. Most commonly use are

Test Director: which is used to record requirement, preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases.

Mercury Load Runner: is used for performance testing. This is an automatic tool.

What does the following terms means : 

• - Technical Unit Testing 
• - Functional Unit Testing 
• - Integration Testing 
• - Volume Testing -
• - Parallel Testing

Technical Unit Testing T-est of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed. 

Functional Unit Testing- Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result. 

Integration Testing-Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas. 

Volume Testing- Testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized. 

Parallel Testing-Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared. 

I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several. 

What kind of testings that are carried out in testing server?
1. Individual Testing ( Individually which we've created)
2. Regressive Testing ( Entire Process)
3. Integration Testing ( Along with other integrated modules)

The 3 types of testing is as follows:-

1. Unit testing (where an individual process relevant to a SD or MM etc is tested)

2. Integration testing (where a process is tested that cuts across all areas of SAP).

3. Stress testing (where lots of transactions are run to see if the system can handle the data