Enhancment Before saving document

[Former Member]

Hi Gurus,

Is there is any User Exits or Enahancemets available for delivery or pgi befor saving system has to check certain requirment like for that perticular customer wether we received payment or not.If we received payment system has to allow or system has to give error message .

Thank you in advance .

Regards,

Suresh

[Former Member · Accepted solution]

Hi,

is this Order related Billing Scenario then

Create new routine adding all your requirement in VOFM

Assign that in Copy control - VTLA - Sales Order to Delivery

item -- > order requirement field

so that it will not allow(Creation itself) to copy if the condition is not satisfied which you have written in the Routine

User Exits or Enahancemets available for delivery

USEREXIT_SAVE_DOCUMENT_PREPARE

Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.

The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN

Regards

Senya

[Former Member]

Dear sureshbabusure

please explain scenario in brief

for your each sales order, advance payment compalsary ??? means without advance payment you cannot do the delivery ???

if this is the case

then you can create the down payment request billing document type FAZ and with respect to that billing document you can create the sales order through copy control

or standard solution as use credit management

its depend on your exact requirment

hope it will helpful for you

[Former Member]

Hi,

I am not getting if dont mind can you elobrate it.

Regards,

Suresh

Edited by: sureshbabusure on May 28, 2010 9:26 AM

[former_member131745]

If you are looking for a userexit then I think 'senya_1111' is correct in recommending USEREXIT_SAVE_DOCUMENT_PREPARE (MV50AFZ1).

However, I believe the best solution to this issue would be to use credit management.

You can define any of the following credit checks for various combinations of credit control area, risk category, and document credit group:

Static Credit Limit Check

The customer's credit exposure may not exceed the established credit limit. The credit exposure is the total combined value of the following documents:

- Open orders

- Open deliveries

- Open billing documents

- Open items (accounts receivable)

The open order value is the value of the order items which have not yet been delivered. The open delivery value is the value of the delivery items which have not yet been invoiced. The open invoice value is the value of the billing document items which have not yet been forwarded to accounting. The open items represent documents that have been forwarded to accounting but not yet settled by the customer.

Dynamic Credit Limit Check with Credit Horizon

The customer's credit exposure is split into a static part; open items, open billing, and delivery values (see above), and a dynamic part, the open order value. The open order value includes all undelivered or only partially delivered orders. The value is calculated on the shipping date and stored in an information structure according to a time period that you specify (days, weeks, or months). When you define the credit check, you can then specify a particular horizon date in the future (for example: 10 days or 2 months, depending on the periods you specify). For the purposes of evaluating credit, you want the system to ignore all open orders that are due for delivery after the horizon date. The sum of the static and dynamic parts of the check may not exceed the credit limit.

Maximum Document Value

The sales order or delivery value may not exceed a specific value which is defined in the credit check. The value is stored in the currency of the credit control area. This check is useful if the credit limit has not yet been defined for a new customer. It is initiated by a risk category which is defined specifically for new customers.

Changes Made to Critical Fields

The credit check is triggered by changes made in the document to values in any of the credit-sensitive fields. According to your Customizing settings, the system runs a check credit between changes or differences in the sales order data against the default values in the customer master record. Examples of such fields are terms of payment and fixed value dates.

Date of Next Review

Uses the date of the next credit review as a trigger for an automatic credit check. If you process a sales order after a customer's next review date has already gone by, the system automatically carries out a credit check.

Overdue Open Items

The relation between open items which are more than a certain number of days overdue and the customer balance may not exceed a certain percentage.

Oldest Open Item

The oldest open item may not be more than a specified number of days overdue.

Maximum Number of Dunning Levels Allowed

The customer's dunning level may only reach a specified maximum value.

User-Defined Checks

If you want to carry out checks other than the standard checks, you can define your own checks in the appropriate user exits in Customizing for Sales.

There is very good information available in the F1 help for the above fields in trx OVA8.

I hope this helps.

Gerard

Edited by: Gerard Magorrian on May 28, 2010 2:58 PM

Edited by: Gerard Magorrian on May 28, 2010 2:59 PM

Edited by: Gerard Magorrian on May 28, 2010 3:04 PM

[Former Member]

Hi,

Thank you for giving responce.

Here my clents requirment is they were not bother about previous payments just we received advance payment for that pertcular sales order or not if not dont allow for delivery .

Regards,

Suresh

[Former Member]

Dear,

It is done in sales order. If you maintain your customer in FD32 and maintain risk category then it will show error when you save the sales order. It will give you credit check error if customer have no sufficient balance to do the error and if he has balance then no error comes.

Hope it will help you.

Regards,

Sandip