Common COGI Errors
Common COGI Errors
Use the check box 'Manual' in pricing procedure in SPRO. Path: IMG->MM->Purchasing->Conditions->Define price determination process-> Define calculation schema Select your pricing procedure and go to control data
Pls tell me how many pricing procedure in MM? Which are they & how to configure? Pls suggest me. There are two types of procedure 1)TAXINJ -Conditioon & formula based 2) TAXINN condition based. TAXINN is the widely used as for advantges its flexibility. The same is give below. The Basic thing is Condition Technique. In which there are 1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table.
A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a Condition Technique.This is a simple logic
Here the Condition Type is very important like PB00, PBXX,RA01 etc.
In the background every Condition Type has its own defition means the purpose of the Condition Type like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions.
Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement.
The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement.
Ex. RA01 - Discoount % is caclulated on PB00 - Gross Price means RA01 is based on PB00 like that we have to define in the Pricing Schema which makes easy to use in realtime. Here PB00 has the Access Sequence - 0002. But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types.
In the system, by default some standard Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define.
For the configuration, I may not able to explain properly through here but will give some Idea.
Configuration: SPRO-IMG-Material Management- Purchasing- Conditions-Define Price Deternmination Process 1. Define Access Sequence 2. Define Condition Type 3. Defince Calculation Schema:- Here you have to define the Schema Define Schema group 1. Define Schema Group vendor 2. Define Pricing Schema group 3. Schema group for Purchase Organisation 4. Assign Schema group to Purchase Organisation
Define Schema determination 1.define calculation schema for Standard purchase organisation
After completion of the Schema Group, we have to assign it to Vendors. Then whenever we use any transaction with this Vendor, the concerned Schema will work as configured by us.
We often find questions related to Backflushing & COGI errors (Errors in Automatic Goods Movements during Confirmation entries). Let's recollect certain Basic details Goods movements can be created during the confirmation entry for the Production/Process order. Backflushing
If you confirm an order / operation with components that have the Backflushing indicator set, the system automatically posts a goods issue for these components. For more information about the Backflushing indicator, refer to the end of this section. Automatic Goods Receipt If the control key of the operation being confirmed specifies automatic goods receipt, the system automatically posts the produced material to stock. Automatic goods receipt can also be activated by the production scheduling profile. Automatic goods movements are not permitted for materials that require serial numbers. However, if an automatic goods movement is specified for a material that requires a serial number then an error record is written. This error record can be displayed using the reprocessing function but it cannot be posted. Error records for materials that require serial numbers must be deleted manually. The goods movement must then be executed manually in inventory management. Backflushing Indicator We can control backflushing in the following objects: Material master - Backflushing key (MRP2 view) Work center - Basic data screen. This is only taken into account, if the material master stipulates that the work center should determine whether the material is backflushed. Work centers are assigned to a production order via the operations. The operations are copied from the routing used. Routing - component overview. This indicator is always taken into account, irrespective of the indicators in the material master or work center. If the Backflushing indicator has been maintained in the master data, it is copied from there when you create a production order. You can change the indicator in the production order Incorrect Goods Movement If errors arise during a goods movement for certain reasons(for example, during backflushing insufficient stock is available in the warehouse) then you can either process the incorrect goods movements directly in the confirmation transaction or separately using a reprocessing function.
o o
Correction in the confirmation In Customizing for Confirmations (OPK4 - Goods movements indicator in the Error handling/logs area) you can define that, for individual entry of confirmations, the system displays an error log before it saves a confirmation with incorrect goods movements. Before you save the confirmation you have the option of correcting the incorrect goods movements. Correction when reprocessing
If you want to process incorrect goods movements at a later stage, you can use the reprocessing function (COGI/CO1P)
The table AFFW shows the list of Goods Movements with Errors from Confirmations We can clear many of the regular errors by setting up a batch job to run the program CORUPROC at defined frequency.Still, we need a regular manual intervention to check to clear the residual errors using transactions COGI (or CO1P), left behind after the batch job execution. This is an attempt to prepare the list of Common errors seen in COGI and respective resolution actions. Kindly feel free to suggest changes / additions to the list. Listing few of SAP notes which could be useful reference, while analyzing the Goods movement errors -
Note 540392 - FAQ: Automatic goods movements Note 545749 - COGI: How to correct certain errors Note 603615 - Old AFFW records can neither be processed in COGI nor CO1P Note 1631357 - Deletion of obsolete failed goods movements
Note 730840 - Consulting: All goods movements receive the same error While searching around, found another nice blog on COGI, by Tanya Duncan. Sure, many would find this an useful
reference as well.
Thanks. Senthil
ERROR TEXT
RESOLUTION a.Add inventory to the respective Storage location & then post COGI b.Change the Storage location entry to where the inventory is available a.Enter the Storage location b.Maintain the Issue storage location in Material master or BOM Extend the material to the plant / storage location & then post COGI Change the posting date to current month/date and save
TRANSACTIONS
Storage location field empty Material XXXX YYYY ZZZZ does not exist In plant XXXX , post to current period YYYY/MM
Posting only possible in periods YYYY/MM and YYYY/MM in company Change the posting date to current month/date ( within the code XXXX referred posting period) and save The plant data of the material XXXXXX Wait for or Request the other user to complete / let the is locked by the user UUUUU material off his transactions & then post COGI Material XXXXXXX YYYY ZZZZ blocked due to a physical inventory User Authorization Errors for certain movements Enter a vendor for special stock Current order status does not allow goods receipt Enter valuation type Wait for the Physical inventory process to be completed / Request the Supervisor to clear the physical inventory & then post COGI Get necessary authorization to the user / Post the transaction using the other users with the right authorization settings Enter a vendor for the special stock (K,P) on the COGI detail screen Check the Order and reset the status (like DLFL/CLSD) temporarily. to allow goods movements Enter the valuation type on the COGI detail screen
COGI Wait for the unlocking & then post COGI MI** COGI