CO-PA, is credit management suppose to block orders from posting to CO-PA?

We are currently using CO-PA to track the $ amount of sales orders that were booked for a particular date range, and it will show the sales order created or changed and the $ amount that was added or taken away from the bookings for that day. This report is to show management how much sales has been recorded for the day, but not necessarily shipped out yet.
What we are currently facing is problems with credit management blocking the order from posting into the CO-PA tables. When the order is created and the order desk hits save it first goes through credit management, and if it is put onto the blocked order lists to be released it does not post the value that was created for that day into CO-PA. Also when we run our rescheduling report for orders that have already been created the order can again go back and forth on and off credit hold, and each time it posts an entry into CO-PA.
I was wondering if anyone has been requested to have a report written to record bookings of sales for a particular day, and have you run into the issue of the credit management posting over and over onto the report and how do you get around this.
We just want to see if any new orders have been created for that day, if current orders have been added on to or taken off from, and have a report to show the order #, dollar value and quantities.
Thank you,
Karen Kim

Dear Karen,
You cannot see blocked SD documents for credit check in CO-PA. Values are transfered to CO-PA after the sales order is processed or after the billing document is posted. So if the sales order is not
processed because it is blocked for credit check, naturally it will not be transfered to COPA. The logic to exempt orders on credit hold was implemented in release 40A.
To overcome your problem you may implement the modification described in the note 214059. Please be aware that this is a modification note. Please implement in a development environment first and retest.
regards
Waman

Similar Messages

Credit Management for different Sales Order Types

Hello All,
The problem is related to Credit Management for Sales Order which is explained below with an example -
We have separate Sales Order Types for New Launches (ZNLS) & Normal Depot Sales (ZDPS) but both the Order Types are assigned with same pricing procedure and respective orders will be raised against the same party code.Now automatic credit check is only active for order type ZDPS where the credit limit had been set to Rs.1000. Now Rs,.500 had already been raised using order type ZDPS, then another sales order of Rs. 500 is raised using order type ZNLS.But when a sale order of Rs. 550 is raised using order type ZDPS the sales order is getting blocked, because the system had taken into consideration & added up the Rs. 500 value of ZNLS with previous value of Rs. 500 against order type ZDPS as a result of automatic credit check though it is not active for order type ZNLS.Point to be noted that Credit exposure is also not active for Order Type ZNLS.
How is this taken into consideration & what are the steps need to be configured so that the credit limit check will not get automatically activated for order type ZNLS and only remain active for order type ZDPS despite they are assigned to same pricing procedure and used for invoicing same party code?
Please suggest.
Thanks & Regards
Priyanka Mitra

Hi Mitra,
The issue occurs because of the fact that credit check and the
update of the credit values are separate processes which are also
controlled separately by the respective customizing:
1. credit check is controlled by transactions OVAK and OVA8.
According to the attachment, you have already refered to note 18613 to
check the customizing settings.
2. update of the credit values is controlled by VOV7 or OVA7: "credit
acttive" flag. The 'Credit active' setting only affects the credit
update of the SD credit values (open orders, open delivery and open
billing documents). This flag has no control on the credit check. So
if for an order type, there is no credit check in OVAK and OVA8 but
the "credit active" flag is set for the item category, the order will
update the credit values even if no credit check is performed for the
order.
If the flag "credit active" is not set, the system will not update the
open credit values. On the other hand, the system ALWAYS updates the FI
credit value 'Open receivable' when the billing document is transferred
to Accounting. So, although you deactivated the "Credit active" flag in
in OVA7 or VOV7, such an item will increase the 'Open receivables' and
thus the credit limit used when the corresponding billing document is
posted to Accounting.
If you would like the value from sales order type ZNLS is excluded from credit update, you could consider set the "Credit Active" field as blank in VOV7 for the item category used for ZNLS.
Best regards,
Smile

Credit management for Old sales orders

Hi experts,
pls consider the follwing example where i am facing some problem.
I activated the Credit lock system in Sales order level (Warning message with release strategy)and in PGI. (Warning message with release strategy).
Customer A
C.limit : 10000
Outstanding : 7000
Sales value(Without pending sales order value): 2000
Eli gable new sales order value 1000
Pending sales order value 5000(Sales order no 111)
Now if i process this old SO no 111 in VL01N i am getting error that Order blocked due to credit limit. But i activated dynamic credit control only in sales order and in PGI.Not activated in VL01N level.
Awaiting for your valuable reply.
Thanks
SR

Hi
1.KIndly check in the sales order that you have maintain the payment guarentee procedure because of this the system is not allowing to do the delivery
PATH: VA02sales order no-Go toItembilling document---payment guarentee procedure
so kindly check that and remove or assign the financial document to that for processing the billing
2.Check the credit lock procedure is release or not
By doing above the issue will be resolved,kindly check and confirm.
if you have any further clarifications let me know
REgards
Damu
KIndly check the belwo

Credit Management doesn't release hold from order (11i)

Hi guys...
In some cases Credit Management doesn't release the hold from order automatically.
I'm debugging CM Workflow and I didn't find anything.
So in these cases we need to force it by executing a custom concurrent.
I've found some open bugs at metalink but I'd like to know the reason for that.
Anybody knows?
Tks
Best Regards,

I have a very similar problem:
I wrote an application that uses SAP DI and writes many dozents of draft documents. It doesn´t make a difference if I set
objDoc = objCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDrafts) for each document or not: every document leeches round about 2-4 MB. That is, in case of an import of 100 documents, up to 400 MB are used.
Isn´t there a possibility to minimize the volume of leeched memory?
Info: I´m using DI and UI, but I am filtering ANY Events from the UI (just need it for singel-sign on).
regards,
Marian

Credit management module at Sales order creation

Hello Folks,
Can I confirm that when a sales order is created and customer master data code entered, eg , Payer or sold-to party or ship-to party, SD will integrate with Credit management module and do a credit check even before sales order is saved?
Likewise, at order creation stage, SD can also integrate with Project system for milestone billing?
With MM, SD checks the availabilty of material at order creation.
SAP SD integrates with CO only at PGI (via table 30 of MM ) and billing stage.
regards
Tom

The Credit Management check only for the payer's credit. The Credit Check can be configured to check even before the sales order is saved.
Goto T.Code OVA8 or SPRO>Sales & Dist>Basic Functions>Credit Management/Risk Management>credit management>Define Automatic Credit Control
Here you can configure. Check the field Item Check on the top left hand side.

Credit management in stock transfer order

Hi experts,
For export billing scierio
we are doing stock transfer order from our main plant to ship yard( dock plant) with excise invoice , and doing final invoice in SD when actual shipment is made from dock yard.
Our requirment is to have a credit mangement check when material is getting transfered from main plant to dockyard through Stock transfer order ( UB) . Can any one help me regarding this.
Regards,
KC Choudhury

Hello KC Choudhary,
I have seen that your business process consists on a Purchase Order and a Delivery but with no Sales Order (VA01). Unfortunately I regret to tell you that in the standard it is mandatory to have a sales order if you want to perform a
correct credit check in the delivery. There are several data needed from the sales order which are not available in the delivery. All the data for the delivery should come from the sales order (like the payer -> credit account). If there is no sales order, these data is not available and therefore no credit check can be performed. A credit check in delivery without related sales order is not possible in the standard system. There is no userexit availabe to achieve this functionality either.
Regards,
Raghavendra YN

Is Verizon blocking me from posting to my Google group

I am a new administrator ( of several) on our organization's Google group which is used only for delivering messages to the group. Evan though I have permisions as an administrator to post and other managing functions, I am unable to post a new message from my verizon.net or gmail emails. Any help is apprciated.
D.

Will this help you ?
https://support.google.com/a/answer/167085?hl=en
Tom
Freedom Essentials, QIP 7100 1,Bose SOLO TV Sound System,,QIP 7216 P2,M1424WR Rev F, iPad 2 WiFi,iPhone 5,TV SYST INFO Release 1.9.5 Build No. 17.45
Data Object 39.45

Blocking Users from Posting

Hi,
We are auditing this company and we noted that there are three dormant company codes. They became dormant because these companies were already dissolved and liquidated. Currently. these three are set to non-productive.
My question is: Is there a way to block users, who have access to all company codes, from posting to these company codes? I was hoping maybe there is some configuration that will prevent the users from posting any transaction to these company codes. We don't want to clean up the roles since this is a big exercise.
Appreciate if you can help me on this matter.
Thanks in advance.

Post it in Netweaver--- security forum.
For your question..I think it can be done through configuration...If there is no existing company code..how can they post?

Credit management how to block amount on particular sales order

hi,
Client want to block amount on sales order.
If customer is having credit limit of 100000 n there are 3 sales order , sales order 1 amount is 50000,sales order 2 amount is 30000 and sales order 3 amount is 40000...
Now customer is coming n saying I want 40000 amount material of sales order 1.here my client want to block 50000 for sales order 1 so customer can not use amount for other sales order , system will check credit limit is 100000 and out of 100000 system should block 50000 for order 1.
Solution required...
If this is not possible then suggest me possible solution.
please suggest...

please note what you require is not possible in SAP.
Therefore there is no standard solution.

Credit management –impact in sales order if the order quantity is above customer credit limit..

Hi Team,
Can anyone help us to solve the issue in credit control process..our requirement is stock reservation should happen in sales order even if the sales order value is above the limit in customer master..
Please share the configuration ..
We tried many things but not working properly..
Thanks,

Hi Shiv,
thanks for the help
in this note , the point number 9 mentions that the result of rescheduling and manual stock reservation will be different if there is credit check in sales order.
is there any way to solve it? it is because our product list is so high..i run V_V2 for 1000 items for 800 items reservation happened propelry and for 200 V_V2 didnt confirm for some orders for the same do we need to run manual ATP??
Thanks to help us

MIRO - How to block system from posting to 2 different vendors

Hi,
Is there a way in the system to prevent parking/posting an invoice document in MIRO which has multiple Purchase Orders that belong to different vendors? I can't seem to see any configuration settings that would enable the system to display an error/warning message to block the transaction.
Thanks and regards

>
Patrick wrote:
> Hi,
>
> Is there a way in the system to prevent parking/posting an invoice document in MIRO which has multiple Purchase Orders that belong to different vendors? I can't seem to see any configuration settings that would enable the system to display an error/warning message to block the transaction.
>
>
> Thanks and regards
Check SAP Note 393431 - MIRO - Vendor
Select it by vendor in MIRO.

Credit management not updated for the first credit blocked order only

Hi experts,
Pls help to solve. Thx.
Case: The first sales order is created against credit block because the credit limit is exceeded. In FD33, no credit data related to the first order indicates, i.e. credit limit used shows zero as well as sales value, credit exposure. In VKM1, the blocked order can be captured.
As long as the second order is created, the credit management can be updated. But, it still does not capture the data from the first order.
The sales orders I test have the same delivery date.
Questions:
1. Is the standard behavior for the dynamic credit check?
2. If not, how to make credit management consider the first order data?
PS. In OVA8, update 000012 is applied while horizon is 4 months.

Hello Jonathan,
After testing, I found credit management can consider the first order data if using 000018 only. Why 000012 cannot consider it?
I have checked the explanation for those two update groups by F4. I feel obscure about the explanation of sales order between them (see below).
000012:
Sales order
Increases open order value from delivery-relevant schedule lines
000018:
Sales order
Increases open delivery value
By the way, my testing data as below:
1. were the two sales orders of the same document type? Answer: yes. Same document type, same customer, same delivery date, etc.
2. were the item categories the same? if not, was one not relevant for credit check? Answer: Yes, the same.
3. did the documents have the same value? if the second order had a lower value and was not blocked for credit, the exposure will be updated. Answer: yes, credit management can consider the second order data ONLY. It seems the first order have not been created if checking credit management.

Credit management urgent

Dear sap gurus,
after implementing credit management in middle or not from beginning and if you want to have the history a particular customer updated in LIS or if we want to know about his credit exposure.
What should be done.Kindly help me.
regards,

How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Difference Between Simple and Automatic Credit Check Types
In automatic check, difference between static and dynamic checks.
SIMPLE CREDIT CHECK : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1,00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options : A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK : Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION :Checking Group + Risk Catageory + Credit Control Area.
A) Credit Checking Groups : Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Catageory : Based on the risk catageories company decide how much credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003) : Average Credit
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
DYNAMIC CREDIT CHECK : 1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the lost 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check(0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
Set Up for Credit Card Payment Processing
Given below is the set up for credit card payment processing:
Set Up Credit Control Areas:
Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be u201800012u2019. This entry is required so the sales order will calculate the value to authorize
Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code
Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: u201CAu201D
Reqt: u201C2u201D
AltCTy: u201C4u201D
Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field u201Cno Credit Checku201D with the valid number for sales documents.
Set Up Payment Guarantees
Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form u201C02u201D defined for payment cards. Other than the descriptor, the only other entry should be u201C3u201D in the column labeled u201CPymtGuaCatu201D
Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number u201C1u201D
Payment Guarantee Form u201C02u201D
Routine Number u201C0u201D Routine Number can be used to validate payment card presence.
Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = u201CPayment Card Payment Cards (All Customers can use Payment Cards)u201D.
Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards
Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
Payment Card Configuration
Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etcu2026)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
CC Credit Cards No-check No-check
PC Procurement Cards No-check Check
Determine Card Categories
Transaction:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.
Visa Credit Expires in 7 days.
400000 405500
405505 405549
405555 415927
415929 424603
424606 427532
427534 428799
428900 471699
471700 499999
Visa Procurement Expires in 7 days.
405501 405504
405550 405554
415928 415928
424604 424605
427533 427533
428800 428899
Mastercard Credit Expires in 30 days
500000 540499
540600 554999
557000 599999
Mastercard Procurement Expires in 30 days
540500 540599
555000 556999
American Express Credit Expires in 30 days
340000 349999
370000 379999
Discover Card Credit Expires in 30 days
601100 601199
Set Sales Documents to accept Payment Card Information Transaction:
Tables: TVAK
Action: Review the listing of Sales Document types and enter u201C03u201D in the column labeled u201CPTu201D for each type which can accept a payment card
Configuration for Authorization Request
Maintain Authorization Requirements
Transaction: OV9A
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
Define Checking Group
Transaction:
Tables: CCPGA
Action: Define a checking group and enter the
description. Then follow the below guidelines for the remaining fields to be filled.
AuthReq Routine 901 is set here.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
(Insight does not use auth horizon period).
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.
Assign Checking Group to Sales Document
Transaction:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards
Define Authorization Validity Periods
Transaction:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.
AMEX American Express 30
DC Discover card 30
MC Master card 30
VISA Visa 7
Configuration for clearing houses
Create new General Ledger Accounts
Transaction: FS01
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.
Maintain Condition Types
Transaction: OV85
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence u201CA001u201D
Define account determination procedure
Transaction: OV86
Tables: T683 / T683S
Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step.
Assign account determination procedure
Transaction:
Tables:
Action: Determine which billing type we are using for payment card process.
Authorization and Settlement Control
Transaction:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
Enter Merchant IDu2019s
Transaction:
Tables: TCCM
Action: Create the merchant idu2019s that the company uses to process payment cards
Assign merchant idu2019s
Transaction:
Tables: TCCAA
Action: Enter the merchant idu2019s with each clearinghouse account
Reward points if useful.
Regards,
Anbu

Blocking Customers From Placing Orders

Hi,
ould like to block certain customers from placing orders. How can I do this?
Thanks,
Mounika.

Hi,
You can apply the block based on sales areas using VD05, but you would have to block the customer in the all areas that the order could be created against. If you want to block the customer globally, use XD02 - Extras - Blocking Dtat. There you will see:
Sales order block
-All sales areas
-Selected sales area
Delivery block
-All sales areas
-Selected sales area
Billing block
-All sales areas
-Selected sales area
Block sales support
You can also block deliveries and billing at this level.
You can also try blocks in credit management and accounting using FD05 and FD32.
You can block orders from being created and shipped in Credit Management with a whole host of settings here including blocked or various risk categories
Reward points if found helpfull...
Cheers,
Siva.

Report generation for Delivery Blocked Orders

Hi All,
I am trying to pull up a report which should contain only orders with the Delivery Block.
Through VL06O i can get the orders which need to PGIed, which are open, which are stuck in workflow and which have got delivery block.
So is it possible to separate the delivery blocked orders (from an end user point of view) from the other orders. I tried to have a look at the filters which i could put on the VL06O-> Outbound Deliv. for PGI, but couldn't find it.
can any one help in thi regard.
Thank you in advance.

Hi,
Try report V.02 - Incomplete Orders

CO-PA, is credit management suppose to block orders from posting to CO-PA?

Similar Messages

Maybe you are looking for