Thursday, September 10, 2009

Planning-Vers.-Depend. and Planning-Vers.-Independ. Master Data

Background documentation Planning-Vers.-Depend. and Planning-Vers.-Independ. Master Data Locate the document in its SAP Library structure

The following sections contain information on which master data is planning-version-dependent and which is planning-version-independent.

Global Product Master

The data in the global product master is independent of a planning version.

Location

By choosing a planning version and the change mode on the initial screen for location master data maintenance, you can process all fields that are dependent on the planning version.

For more information, see Displaying, Creating and Changing a Location.

Location Product

By choosing a planning version (via Extras ® Choose Planning Version) and choosing the change mode on the initial screen of the location-specific product master, you can process all fields that are dependent on the planning version.

If you did not choose a planning version on the initial screen, the values you specified in the planning-version-dependent fields will automatically be assigned to planning version 000 (this applies in any case to planning-version-independent fields).

If you change the planning-version-dependent data in the location product master without explicitly specifying a planning version, you will also change the planning-version-dependent values of version 000 and all versions for which no planning-version-dependent data has previously been defined.

Only the location products for which you have explicitly created planning-version-dependent data use separate data and not the planning-version-dependent data of planning version 000.

For more information, see Maintaining Location-Dependent Product Master Data.

Production Process Model (PPM)

Time-dependent parameters of a PPM are dependent on the planning version. You can define time-dependent parameters in the PPM for the following data:

· Scrap of an activity

· The duration of an activity defined at the mode

· The capacity requirement of an activity defined at the resource

· The material consumption defined at an alternative component

If you define one of these parameters dependent on time, you can specify a planning version for which this setting is valid.

· If you specify a planning version, the system only uses this setting for the specified planning version.

If you copy this planning version, the system also copies the time-dependent parameters. If you change the parameters in the original planning version later, this has no effect on the parameters of the copy.

· If you do not enter a planning version, the system uses this setting for all planning versions for which you have not defined any other time-dependent parameters. If you change this parameter, this also affects all planning versions for which you have not defined any individual settings.

If you copy a planning version for which no planning-version-dependent data and no time-dependent parameters have been defined, the copy also uses this information.

For more information, see PPM Plan.

Resource

All the data of a resource is dependent on the planning version. Specific data for the resource, such as the resource type, cannot be changed; some data can only be changed depending on the status of the activities scheduled on the resource.

If you assign a resource to a model, the system automatically assigns it to all planning versions of this model. If you create a new planning version for this model later, the system also automatically assigns the resource to the new planning version.

If you change the data for a resource, you only change it in the planning-version-specific copy; in other words, if necessary, you have to change the data in all planning-version-dependent copies of the resource.

Note

On the initial screen of the master data for the resources, you can copy the resource data of all planning versions of a model via Tools ® Copy Resources.

Behavior of the planning-version-dependent resource master data when a planning version is copied

Source version

Copy

Planning version 000 without separate planning-version-dependent data

Not possible

Planning version 000 with separate planning-version-dependent data including capacity variant data; uses the data of the shift definition

Separate planning-version-dependent data, separate variant data; uses the data of the shift definition

Planning version XYZ without separate, planning-version-dependent data

Not possible

Planning version XYZ with separate planning-version-dependent data including capacity variant data; uses the data of the shift definition

Separate planning-version-dependent data, separate variant data; uses the data of the shift definition as in the source version

For more information, see Creating and Changing Resources.

Quota Arrangement

All quota arrangements can be defined as dependent on the planning version. However, you can also define planning-version-independent quota arrangements. Planning-version-independent data is used in all quota arrangements for which there is no planning-version-dependent data.

If you wish to explicitly assign quota arrangement data to planning version 000, you must specify the planning version 000 while in quota arrangement maintenance mode (Master Data ® Quota Arrangementsfrom the SAP Easy Access screen). If you change this data, the change will have no effect on other planning versions.

If you copy a planning version for which no planning-version-dependent data has been defined, the copy contains no planning-version-dependent data and also uses the planning-version-independent data.

If you copy a planning version for which separate, planning-version-dependent data has been defined, this data is also copied. If you change the original version (after copying), this change has no effect on the data of the copy.

If you copy planning version 000, all planning-version-dependent data is copied at the same time. If you change the data in planning version 000, this change has no effect on the data of the copy.

Changes to the planning-version-independent quota arrangement data affect all planning versions for which no planning-version-dependent data has been defined.

For more information, see Validity of Quota Arrangements.

Source: http://help.sap.com/saphelp_scm50/helpdata/en/88/1fe93b7f1f954ce10000000a114084/content.htm

Tuesday, September 1, 2009

Note 1250385 - DP Job cancellation triggers abend of the process chain

ummary
Symptom

A Batch Job executed within RSPC gets status "cancelled" because an error occured. In this case, the whole process chain stops, even if the link to the next process was set to "always".

Other terms

/SAPAPO/TS_BATCH_RUN; RSPC; SM37 job log

Reason and Prerequisites

When SM37 status is set to "cancelled" (red), an exception ERROR_MESSAGE with an abend is triggered.
This causes the whole process chain to stop.

Solution

Currently, the only alternative is to avoid setting the job's status to cancelled when possible.
This is what this note is doing.

Header Data



Release Status:Released for Customer
Released on:12.03.2009 14:38:17
Master Language:English
Priority:Correction with high priority
Category:Program error
Primary Component:SCM-APO-FCS-MAP Mass Processing

Affected Releases

Software
Component
Release
From
Release
To
Release
And
subsequent
SCM
410
410
410

SCM
500
500
500

SCM
510
510
510

SCM
700
700
700

Correction delivered in Support Package

Support
Packages
Release
Package
Name
SCM
410
SCM
500
SCM
510
SCM
700

Corrections Instructions

Correction
Instruction
Valid
from
Valid
to
Software
Component
Last
Modifcation
410
410
SCM
11.03.2009 13:54:52
500
500
SCM
11.03.2009 13:55:56
510
510
SCM
11.03.2009 13:56:47
700
700
SCM
12.03.2009 14:19:59

Related Notes




1180107 - Background job gives errors but the job log has green status

1127476 - Background job ends with a dump, but job log status is green

Friday, August 28, 2009

Role of SAP Consultant In Testing

source: http://www.sap-img.com/general/role-of-sap-consultant-in-testing.htm

Role of SAP Consultant In Testing

1. What is the role of SD Consultant in Testing while implementing the project?
2. What is Unit testing and Integration Testing?

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 mathologies 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
- IntegrationTesting
- Volume Testing
- Parallel Testing?

Technical Unit Testing= Test 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.

IntegrationTesting= 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)

Tips by: Teresa Pittari, Gregrobinette

Thursday, July 30, 2009

Configure Transfer to OLTP Systems

SIMGAPO_SNP_SNP110

IMG, Advanced Planning and Optimization->Supply Chain Planning->Supply Network Planning (SNP)->Basic Settings->Configure Transfer to OLTP Systems

Use

In this IMG activity, you set how orders that are created, changed, or deleted during SNP planning, are transferred to an OLTP system. The following options are available:

  • No Transfer: The orders are not transferred to an OLTP system.
  • Immediate Transfer: The orders are transferred to an OLTP system immediately during SNP planning.
  • Periodic Transfer: The orders are first collected together and are then able to be transferred to an OLTP system using the CIF (APO Core Interface) transaction Process Change Pointer.

You can also exclude certain types of orders from transfer, such as SNP stock transfers where no source location exists.

For the processes of aggregated planning and planning with aggregated resources, you can define which orders you want to be transferred that were created at the different levels of a location product hierarchy. The default value is that only the orders for the sub products (suborders) are transferred.

For deployment, you can also specify whether you want the deployment stock transfers generated in the deployment run to be transferred to the OLTP system as a stock transport requisition or a stock transport order.

In addition, it is still possible to choose between a Vendor Managed Inventory (VMI) scenario and a non-VMI scenario.

Dependencies

If you have specified that you want deployment stock transfers to be transferred as stock transport orders to the OLTP system, they cannot be planned again or changed.

Note that the settings you make in the CIF transaction User Settings, can overwrite the settings made here. The following rules are valid:

  • CIF setting Default: The settings that are made within this SNP IMG activity are valid.
  • CIF setting Collect changes: The orders are first collected (periodic transfers). The CIF setting overwrites the SNP setting.
  • CIF setting Do not collect changes: The orders are transferred immediately during planning. The CIF setting overwrites the SNP setting.

If you set No transfer in this SNP IMG activity, the orders are not transferred, even if another setting has been made in the CIF transaction.

Wednesday, July 29, 2009

How to delete material master in APO?

How to delete Material master in APO? (I have material and location)?
How do we delete the transaction data and dependent master data?

This is not a plain thing to delete a product master/location product in a production system.

You have to carry out the following steps:

1. Pre-steps:

a) Remove product from integration model

b) Delete all orders for this product-location which still exist in the APO system by running the reports /SAPAPO/RLCDELETE or /SAPAPO/DELETE_PP_ORDER (this report is not recommanded to be used in product system!!) or transactions /SAPAPO/RRP4 or /SAPAPO/RRP4.

c) Use transaction /sapapo/ccr to delete all objects in APO that are integrated with R/3. The /sapapo/ccr will show the orders as 'Not in an active integration model' and offers to delete the orders in APO

d) Delete the product from ATP tables by running the report /SAPAPO/SDORDER_DEL with the selection according to the product being deleted.

e) Delete all related product substitution and location product substitution using the transaction /SAPAPO/RBA04;

f) Delete the product from all PPMs through the transaction /SAPAPO/SCC05;

g) Remove the product from external procurement using the transaction /SAPAPO/PWBSRC2;

h) Remove the product from transportation lanes through the transaction /SAPAPO/SCC_TL1 or /SAPAPO/SCE; Note: If the lane was created with option 'All products', you should not care about this condition.

i) Remove the product from quota arrangement through the transaction /SAPAP/SCC_TQ1;

j) Remove references from the product master or the location product master using the transaction /SAPAPO/MAT1, tab 'Classification';

k) Remove the planning package from the location product master using the transaction /SAPAPO/MAT1, tab 'PP/DS';

l) Remove the product from RTO;

m) Remove the product from product split.

2. Mark deletion flag

a) In transaction /SAPAPO/MAT1, select the product (and location in case of location product);

b) In the menu bar, choose 'Product' and go to 'Mark for deletion' (Shift+F6);

c) In the popup 'Set deletion Flag' set a flag in the appropriate field: Leave the field 'Product' empty unless you want to delete the product master, i.e. in case a location product must be deleted, the flag has to be set on location only;

d) The deletion can be executed directly or be scheduled for another time.

Source: http://www.sap-img.com/apo/deleting-material-master-in-apo.htm

Note 1058871 - Poor performance of product allocation check

Summary

Symptom

During an ATP check in SCM with product allocation as one of the step in basic methods, bad performance or response time is too high. This is due to the number of characteristic combinations to be checked during the allocation check.

Other terms

Performance, response times, product allocation check, PAL.

Reason and Prerequisites

Number of characteristic combinations and direct connection to planning area. Product Allocation Check is performed in SCM.

Solution

If the performance of ATP check due to allocation check has longer run times please check the following -

- The number of characteristic combinations.
- Check if setting direct connection to planning area is defined in product allocation group.

When the characteristic combinations have reached 100,000 try to reduce them to improve performance. If it is not possible to reduce the number of characteristic combinations deactivate direct connection to planning area in the prodcut allocation group. This will improve the performance of allocation check.

If connection to planning area is deactivated, data between planning and allocation tables has to be synchronized by copying planning data periodically to allocation tables using transaction /SAPAPO/ATPQ_PAREA_R to reflect changes in allocation quantities (KCQTY) and also transfer data to planning area using transaction /SAPAPO/ATPQ_PAREA_W to update incoming order quantities (AEMENGE).

Header Data



Release Status:

Released for Customer

Released on:

25.05.2007 16:56:11

Master Language:

English

Priority:

Recommendations/additional info

Category:

Consulting

Primary Component:

SCM-APO-ATP-BF-PAL Check against Product Allocations

Secondary Components:

SCM-APO-ATP Global Available-to-Promise

Tuesday, July 28, 2009

Note 676128 - Product allocations: Product allocation assignment check

Summary

Symptom

You execute the correction report 'Correct product allocation assignment'.
You can find the report in the SAP Menu under 'Advanced Planning andOptimization' -> 'Global ATP' -> 'Environment' -> 'Product Allocations' -> 'Repairs'.

Other terms

Product allocation, APO product allocation assignment, ATP, QUOT, report: /SAPAPO/RMQUOT_USAGE_CHECK, /SAPAPO/SAPLATPQ_REPAIR

Reason and Prerequisites

  • The incoming orders quantity is the total of the reserved product allocation quantities in a period. The incoming orders quantity cannot be assigned to any individual document. The incoming orders quantity is stored in the same time series as the product allocation quantity.

You can normally display the incoming orders quantity in the planning tool (for example, Demand Planning) together with the product allocation quantity. It should not be manually changeable there.

The incoming orders quantity is subtracted from the product allocation quantity in the product allocation check. The rest is available to the document that was just checked.

If the incoming orders quantity is greater than the product allocation quantity in a period, the product allocation quantities in the adjacent periods are reduced in accordance with the product allocation settings.

If the incoming orders quantity was manually reduced (or not fully updated), this may result in an overconfirmation when you change the document during the repeated availability check.

  • The product allocation assignment is equivalent to a where-used list of the product allocation quantity. The product allocation assignment is stored for each item (for which a product allocation check was carried out).

The product allocation assignment is created when you execute the product allocation in the availability check. The product allocation assignment is always assigned exactly to the time series (special time series or collective product allocation time series) that was used during the check.

The product allocation assignment can be displayed in the product allocation time series display (transaction /SAPAPO/AC42) by double-clicking on the incoming orders quantity. The system first displays all users of the selected period. From there, you can display the entire product allocation assignment for each item.

  • A time series is used in the product allocation to store the product allocation quantity (available quantity) and the incoming orders quantity.

It is identified by a characteristics combination. The product allocation group defines which characteristics are used for this.

  • A characteristics directory, which includes all allowed or defined characteristics combinations, is managed for each product allocation group.

The characteristics directory is used to assign the product allocation time series to the planning time series when you transfer or copy the time series from the Demand Planning.

The check terminates with an error if no defined characteristics combination is found during the product allocation. If the characteristics combination is defined, but no time series or an empty time series is maintained, no quantity is confirmed for this item.

When you search for characteristics combinations or time series, the system only takes into account those with the 'active' status (normal product allocation) and the 'neutral' status (pure update - the quantity requested in the product allocation is completely confirmed). Time series with the 'inactive' status are interpreted as undefined.

You can display and maintain the characteristics directory in transaction /SAPAPO/ATPQ_CHKCHAR. However, you can only create characteristics combinations using the planning tool.

  • Collective product allocations are time series with specific characteristic values. To avoid having to define every possible characteristic combination (as otherwise the check terminates with an error) or having to maintain time series for each of these characteristics combinations, you can use collective product allocations.

If no time series is found for the characteristics combination from the document currently being checked, the last characteristic of the combination is filled with a wildcard character and the characteristics list is then checked again. The search continues until a characteristics combination has been found or all the characteristics have been replaced.

    • If no characteristics combination is found, the check terminates with an error (see above)
    • If a characteristics combination is found, the check is carried out against this combination (see above).

The search for collective product allocation is only carried out at the beginning of the product allocation and is independent of the check result.
Therefore, if an insufficient quantity is found in a time series (the allocation is exhausted), no search is triggered for (additional) collective product allocations.

You can activate the use of collective product allocations for each product allocation step by specifying the wildcard character.
You can use transaction /SAPAPO/ATPQ_COLLECT to generate or add to the characteristics combinations of the collective product allocations.

The total of all product allocation time series (including the collective product allocation) in a product allocation group corresponds to total available quantity in a period.

  • You can change the status of a characteristics combination while the system is running. If you set the status of a special time series (no collective product allocation) to 'inactive', it is no longer visible within the product allocation. The check searches for a collective product allocation and then uses it for the check.

By hiding the time series, you also reduce the total available quantity (see above). You can therefore 'simultaneously' hide the time series and repost the allocations from the hidden time series to the collective product allocation time series (manually, in the planning tool).
However, if product allocations were already taken from the special (now hidden) time series, the corresponding portion is missing in the incoming orders quantity of the collective product allocation time series. These reposted product allocation quantities of the collective product allocation could therefore be debited again.

When you change the status of the characteristic combinations or in the case of those correction possibilities described in the following, the system asks you whether you want to repost these product allocation assignments. The system then reposts the product allocation assignment from the special hidden time series to the next more general 'active' collective product allocation time series.

This transfer posting is only necessary if the product allocation quantities were also reposted in the planning accordingly. If the system only reposted the free product allocation quantities, it is not necessary to repost the product allocation assignment.

In this case, the assignment of the product allocation assignment for the special time series does not disappear (this only applies to the product allocation assignments posted before the status change). You can reactivate the hidden time series. In this case, the correction report takes their product allocation assignments from the collective product allocation time series again and posts them into the special time series.

If a check is run against the special time series when you create a document and against the collective product allocation time series when you change a document, the product allocation assignment is reposted from the special time series to the more general time series. If you reactivate the special time series, you can no longer repost this assignment into it.
Therefore, reposting only allows generalization but not specialization. You can only achieve specialization by using another check, for example, backorder processing (BOP).

Of course, you can also set the status for collective product allocation time series. If a collective product allocation time series is 'hidden', the system searches for a more general time series during the search for a defined characteristic combination (as described above).

Solution

You can use the report to compare (and, if necessary, to correct) the product allocation assignment and the incoming orders quantity.
The sum of the product allocation assignments of a period is generally equal to the incoming orders quantity in the time series.
You can use the report to check (and, if necessary, correct) this consistency under different aspects. You have the following options:

  • Assignment without incoming orders quantity
    The total of the product allocation assignments in a period is compared to the incoming orders quantity in a time series. The result of this comparison is displayed with a traffic light.
    • green Both quantities correspond.
    • yellow The incoming orders quantity is greater than the total of the product allocation assignments.
      This situation may occur, for example, as a result of a relocation of the product allocation from R/3 into APO. The incoming orders quantity could also have been deliberately increased to reserve a product allocation quantity.
    • red The incoming orders quantity is smaller than the product allocation assignment.
      This situation may occur if you manually reduced or did not fully update the incoming orders quantity.

To correct the incorrect periods, you must select all periods of a time series. Use the 'Combine product allocation assignment' function ('Goto' in the menu, or the button) to flag the selected time series for repair.

Then use the 'Execute' function to start repairing the flagged time series.
The system asks:

    • whether you want to transfer the product allocation assignment for the incoming orders quantity.
    • whether you want to add the product allocation assignment of inactive time series for the incoming orders quantity of the more general collective product allocation time series (as described above).
  • Incoming orders quantity without assignment
    The system checks whether the time series contains incoming order quantities to which no product allocation assignment is assigned (also see the yellow traffic light under the section 'Assignment without incoming orders quantity').

The display and functions are identical to those in 'Assignment without incoming orders quantity'.

  • Assignment without order item
    The system checks whether there are product allocation assignments that cannot be assigned to any item.

This situation may occur if the order documents are incompletely deleted (for example, due to notes being incompletely imported) or already archived.

There are two different options for the repair (the deletion):

    • You can either delete only the product allocation assignment (Menu: 'Goto' -> 'Delete individual assignment') without adjusting the time series. The relevant incoming order quantities are then displayed with yellow traffic lights with one of the above options the next time you run this report.

The product allocation quantity assigned up to now remains assigned and cannot be used by other documents. If the items were archived, this procedure is correct.

    • Alternatively, you can delete the product allocation assignment with incoming orders quantity (Menu: 'Goto' -> 'Delete individual assignment with IO quantity'). The incoming order quantity of the relevant time series is reduced accordingly.

As a result, the product allocation quantity assigned up to now is released and can be used by other documents. If the item was not fully deleted, this procedure is correct. Otherwise, this may result in overassignments (if the product allocation quantity can be 'achieved' in accordance with the consumption settings).

The entries selected for repair are flagged with one of these two functions. You can then use the 'Execute' function to start deleting these characteristics combinations or to repair the affected time series.
As described above, the system asks you whether you want to add the product allocation assignment of inactive time series for the incoming orders quantity of the more general collective product allocation time series.

  • Assignment without product allocation group
    In contrast to the previous options, you cannot use the restriction by product allocation groups in this case. The specifications in the selection are ignored.

The system displays all product allocation assignments that:

    • belong to product allocation groups that no longer exist in the Customizing.

These product allocation assignments are created as a result of incomplete system copies, or if the product allocation assignments are not deleted if a product allocation group is deleted in the Customizing.

    • belong to characteristics combinations that are no longer defined in a product allocation group.

These product allocation assignments are created if you delete a characteristics combination from the characteristics directory (for example, when you transfer the characteristics combinations from a planning area (transaction /SAPAPO/ATPQ_PAREA_K), but do not delete their product allocation assignment.

You can select and delete the product allocation assignments in the display. You cannot adjust the time series in the product allocation group. The adjustment is not possible and unnecessary because the assigned characteristics combination of the time series no longer exists, which means that no relevant time series can be identified.

As described above, the characteristics combinations that you want to delete can be selected and then flagged for deletion (menu 'Goto'). You can then use the 'execute' function to delete the product allocation assignments.


You can only use manual entries or actions to execute the report described here. In the case of large product allocation groups, the runtime of an online transaction may be insufficient to execute the report.
You can also use transaction /SAPAPO/ATPQ_KCGRP_U to carry out the time series comparison (as described under 'Assignment without incoming orders quantity').
In this case, the incoming orders quantity is always set to the total of the product allocation assignment of a period (that is, the yellow and the red traffic lights of the above display disappear). You can restrict the area to be corrected to a period of the time series.

Header Data



Release Status:

Released for Customer

Released on:

04.11.2003 16:17:04

Master Language:

German

Priority:

Recommendations/additional info

Category:

Consulting

Primary Component:

SCM-APO-ATP-BF-PAL Check against Product Allocations

Affected Releases

Software
Component

Release

From
Release

To
Release

And
subsequent

SAP_APO

20

20A

20A


SAP_APO

30

30A

30A


SAP_APO

310

310

310


SCM

400

400

400

X

SCM

410

410

410


Related Notes




624539 - /sapapo/sdorder_del: Extended check for allocation


619525 - Display Product Allocation Group using ALV list Grid


569270 - Report /SAPAPO/ATPQ_CHKUSG returns inconsistent line items


553902 - Allocations: Improved performance for prod. allo.


553403 - Allocations: incorrect correction for incoming orders quant.


552140 - Allocations: Performance during LC recovery


527863 - Allocations: Program termination /SAPAPO/RMQUOT_USAGE_CHECK


527153 - Allocations: product allocation check - incorrect display


514199 - Prod. alloc: Order receipt quantity w/o prod. alloc. assgmt


496809 - Allocations: /SAPAPO/ATPQ_KCGRP_U terminates


494607 - Allocations: Product allocation assignment check incorrect


493015 - Allocations: Function error prod.alloc. assignment control


484199 - Allocations: Deleting incoming orders qty during correction


483370 - Allocations: Updating the product allocation assignment


481096 - Addition to consistency check TP/VS for prod. allocat. TDL s


433427 - Allocations: incorrect transfer of characts. combinations


433157 - Product allocations: comparison report (performance)


425825 - Consistency checks, /sapapo/om17, /sapapo/cif_deltareport


422669 - Allocations: Runtime error OBJECT_NOT_FOUND


422042 - Allocations: No display in the comparison report


418949 - Allocations: Incorrect display in the comparison report


412363 - Allocations: Recovery terminates with RFC error


403541 - Product allocations: Runtime error OBJECT_NOT_FOUND


384749 - Prod.allocations:Incoming orders qty not corrected


331512 - Allocations: Incoming orders qty w/o assignment


313717 - Allocations: Runtime error PARAMETER_FAILURE


195366 - Allocations: Loss of order receipt quantity