Email for sales order on credit hold

Hi,
I have a requirement ...
Once the sales order goes into credit hold an email has to go to the customer after next two business days saying that Sales order has been on credit hold
and once the sales order is released from the credit hold an email has to go the customer immediately saying that Sales order has been released from credit hold.
How would we exactly know when the sales order goes into credit hold, I mean can we get the date on which it is changed to credit hold?
how do we calculate two business days from the current date?
Finally is there any exit to write the logic or just write a report and run that in background everyday ?
Please can anyone help me on this...

hi raghu ,
to check whether the date is a working day or not
use the fm
DATE_CONVERT_TO_FACTORYDATE
pass the date as sy-datum
and factory calender id as '01'
if sy-subrc = 0
its a working day
else
its not a working day .
endif.
suppose today is friday and next working day is monday
now if i want to add two business days the final date is on wednesday may be this is referring to procession period time in the sales order .
add 2 to sydatum will fetch u sundasys date which we dont want .
so capture next working date ie mon and add 2
like this
using this fm
GET_WEEK_INFO_BASED_ON_DATE
which will return the week based on sunday and monday .
i/p is sy-datum .
make proper use of the two fms this will help u to build the logic .
regards,
vijay

Similar Messages

Link between sales order to Credit management

Where can we link between sales order to Credit management?

HI Gopala rao.,
In VOV8 sales document type there is <b>credit limit & Credit group</b> Where we asign the credit mage,ment data to Order
The configuration part of credit managemnt is
CREDIT MANAGEMENT:
A credit limit may be a customers credit limit, which is the permitted limit of value of open items, such as invoices not yet paid, plus the value of open sales orders.
The credit limit is the total combined value of the following documents:
Net value of sales order
Open Sales order: order created, but not delivered
Open deliveries: delivered, but not invoiced
Open billing doc: value of billing doc, which has not yet been forwarded to accounting
Open items: forwarded to accounting, but not settled.
Types of Credit Check
Simple Credit Check
Automatic Credit Check
o Static
o Dynamic
Simple Credit Check:
SPRO- IMG- SD- Basic Functions- Credit Mgmt/ Risk Mgmt- Simple Credit Check- Assign Credit Check to Doc Types.
Based on sales doc types
It will check all the above-mentioned docs & if the credit limit exceeds, the system responds in the way defined by you in the configuration menu.
Cannot differentiate according to customer
3 ways to Control the Simple Credit Check:
A: warning
B: error message: the doc cannot be saved
C: warning message with delivery block: the doc can be saved but is automatically blocked for delivery.
Automatic Credit Check:
This credit mgmt control is maintained by using the automatic credit control functionality. The automatic credit control divides the sales doc types, the delivery doc types, & goods issue into specific credit groups. It also uses the customers risk category as assigned to the CMD of the payer & assigns an outcome proc to the combination of the above 2 objects, i.e. the credit group & customer risk category along with the credit control area. The definition of customers risk category is carried out in the fin accounting module.
A customers risk category is a grouping category that controls the credit check when automatic credit control takes place. Thus one can assign high-risk customers to risk category for e.g. A01, medium risk to B01 and low risk to C01.
Automatic credit check divides customers in to 3 categories:
High-risk customers,
Low risk customers &
Medium risk customers.
A credit check can only occur at 3 places: Credit Group
Sales order: for high risk customers
Delivery: for medium risk customers
Goods Issue: for low risk customers
Credit Control Area (CCA): highest organizational element in credit management. A credit control area is an organizational unit that is comprised of one or more company codes. A company code can have no more than one credit control area. Defined by FI.
Menu Path to create Credit Control Area: OB45: FI people.
SPRO- IMG- Enterprise Stru- Definition- Fin Accounting- Define Credit Control Area
Credit Control Area Description
0001 Credit control area 0001
1000 Credit control area Europe
Menu Path to Assign Company Code to Credit Control Area: OB38: FI people.
SPRO- IMG- Ent Stru- Assignment- Fin Accounting- Assign Comp Code to CCA
It is possible to assign Credit Control Area to a Sales Area. This is more specific assignment than the assignment to Company Code.
Company code Company name City Credit Control Area Over write CCA
Menu Path for Defining Risk Categories: OB01: FI people
SPRO- IMG- Fin Accounting- Account Receivables & Payables- Credit Mgmt- Credit Control Account- Define Risk Categories.
Risk Category CCA Name
001 4500 Low risk
002 4500 Medium risk
003 4500 High risk
Menu Path for defining Credit Groups: OVA6
SPRO- IMG- SD- Basic Function- Credit Mgmt/ Risk Mgmt- Credit Mgmt:
Define Credit Groups: OVA6
Assign Credit Groups to Sales Docs & Delivery Docs
o Credit Limit check for Order Types: OVAK
o Credit Limit check for Delivery Types: OVAD
Define Automatic Credit Control: OVA8
Define Credit Croups: OVA6
One merely creates a credit group for each differentiation in the doc type. You enter the credit groups when you configure the sales doc types for credit management & define the automatic credit check. The following credit groups are contained in the standard R/3 system:
01: credit group for sales order
02: credit group for delivery
03: credit group for goods issue
CG (Credit Group) Doc Credit Group
01 Credit group for sales order
02 Credit group for delivery
03 Credit group for goods issue
Assign Sales Documents & Delivery Documents:
Sales Doc Type Descp Check Credit Credit Group
OR Std Order D 01
Delivery Type Descp Del Credit Group GI Credit Group
LF Delivery 02 03
Define for each sales doc type whether a credit check should be carried out. Enter D if an automatic credit check should be carried out.
Specify a Credit Group
Specify a Credit Group for the Delivery Type for which you want to carry out a credit check
Specify a Goods Issue Credit Group for the Delivery Type for which a credit check is to be carried out for goods issue.
SIMPLE CREDIT CHECK CANNOT BE ASSIGNED TO DOCUMENTS.
Define Automatic Credit Control:
One can now assign settings to the combination of the Credit Control Area, the Customer Risk Category & the Credit Group.
CCA Risk Cat Credit Group Credit Control
4500 001 01 Low risk sales orders
4500 001 02 Low risk deliveries
4500 001 03 Low risk goods issue
4500 002 01 Medium risk sales orders
4500 002 02 Medium risk deliveries
4500 002 03 Medium risk goods issue
4500 003 01 High risk sales orders
4500 003 02 High risk deliveries
4500 003 03 High risk goods issue
Select line item and go to details, you can decide whether to do Static or Dynamic Credit Check. Credit Horizon can also assigned here. Additional function checks can be performed here:
A credit check when the maximum document value is exceeded.
A credit check when changing critical fields.
The risk category assignment occurs in the same place as the customers credit limit, which is the customers credit management screen. That is, the risk category is assigned to the customer by the Finance in transaction code FD32.
The customer credit master record is divided in to 5 views:
Overview Screen: gives an overview of credit settings in relation to the customer, including his credit limit, credit exposure, the %tage of credit limit used, his payment data & his risk category.
Address: view gives the customers address details as they appear in CMD
Central Data: is a view that shows the total credit limit the customer can receive across all credit control areas as well as the maximum limit he can receive in one credit control area.
Status: view shows the customers actual individual details according to particular CCA being investigated. This includes his credit limit, percentage used, credit exposure, risk category, whether he is blocked due to credit or not.
Payment history: view displays the payments made by the customer for a particular credit control area where a comp code is assigned.
Static Credit Check Dynamic Credit Check
Net Doc Value Net Doc Value
Open Order Open Order
Open Delivery Open Delivery
Open Billing Open Billing
Open Item Open Item
Compares the total combined values of the above-mentioned documents to credit limit. Plus credit horizon. Compares the values of the following documents to credit limit + credit horizon.
Credit horizon has an attached time period that states that the system is not to include sales orders in the total of outstanding items created after that specified period i.e. for the purpose of evaluating credit, you want the system to ignore all open orders that are due for delivery after the horizon date. Maintained for low & medium risk customers.
Update Groups
Basically it is a info structure where system stores all the data about credit limit. The credit relevant data is updated in a info structure, where it is accessed & updated. Thus each automatic credit control must be assigned an update group.
Update Group 000012
Update Group 000015: delivery & billing
Update Group 000018: sales order, delivery & billing.
Update group 000012, updates at:
Sales doc: increased order value
Delivery: decreased order value & increased delivery value
Billing: decreased delivery value & increased billing amount
Invoice: decreased billing amount & increased open item value.
Release Blocked Sales Order/ Deliveries:
VKM3: sales order
VKM5: delivery
VKM4: both
One can see the offending document. Note on the right hand side, the Status Field. This shows the check, the doc failed. If this field is empty, the doc did not fail a credit check, even though it may be in the list of SD documents that are required to be released.
To release the doc, one indicates the doc to be released and then clicks on the Release Button. The result is the offending doc entry, highlighted green. One then proceeds to save, after which you are informed the doc number has been released.
Net value with sub total A, in pricing proc, will be the basis for credit limit.
REWARD if helpfull
Thanks & Regards
Narayana
Message was edited by:
manam narayana

Dynamic Credit Checks - Different Horizon for Sales Order & Delivery

Hi Experts ,
had a query . I am testing a scenario for Dynamic credit Check where the Horizon is ZERO for Sales Order & 3 Months Horizon for deliveries. How should the system behave in such a case. What would be the best way to test whether system behaviour is ok as per this expectations.
Also I would like to know whether "0" horizon for sales order means that system looks into the entiire list of open sales orders or the horizon of check is only upto the end of the current month . In FD32 the curent date is indiacted as the horizon date. While creating sales orders today I found dynamic block for 0 horizon is only working for sales orders with availabilty date upto 7th July '10 which neither covers the existing month-June & neither full of July. Beyond that there is no dynamic block soccuring.That made me a bit confused .
Please advice with you valuable inputs.
Thanking You.

Hello Sai ,
thank you for the response. Had already checked note . But this does not speak about the implication "0" M horizon of dynamic credit check . What is coverage for that ?

RFC/BAPI For Sales Order Credit Block Release like vkm3 (very urgent )!!

hi experts,
I need the RFC/BAPI For Sales Order Credit Block Release like vkm3 function ,please help
thanks
Godspeed

hi
can get the list of all the bapis..
http://www.planetsap.com/LIST_ALL_BAPIs.htm
Reward if USeful
Thanx & regards.
Naren..

How to implement Approval hierarchy for Sales Order in Order Management.

Hi,
We need approval process for sale orders in Order Management module. Currently we are using credit HOLD option for orders at shipping level. The issue we are facing now is we can not cancel those orders who contains Service Line item in it while on HOLD. The restriction raised at the time of cancelling the order that the Line Item is "fulfilled". Service line item's get fulfilled.
Is that any other possibility to have Approval hierarchy for Sales Orders in Order Management Module? If it is possible can anybody share the related document or implementation guide?
Thanks with anticipation in advance.
Many Regards
Kaleem Bhatti

I copied the standard order header workflow and the "Book Order, Manual" workflow to custom workflows. I then modified the "Book Order, Manual" workflow to put another completely custom workflow (call this "Approvals") in between the "Book Eligible" and "Book" steps.
The "Approvals" step assessed the sales order, changed the order header to the pending approval flow_status_code, and sent out the appropriate notifications. The "Approvals" step returned a Complete/Incomplete where complete would proceed to "Book" and incomplete would go back to "Book Eligible." The new workflow was then assigned to the order type needed. I don't still have access to that environment (job change) or I would give more definite instructions.

Report for released orders from credit block

Dear Friends,
Can you tell me any report which can give us the list of released sales orders from credit block with user ID (who released) and date (when released). If no standard report is availble then please give me the table where this data gets stored, so that I can create a query.
Thanks in Advance,
Sreehari.

Dear Krishnan,
Thank you very much for your immediate response...................
With VBUK-CMGST (D) we can get the list of orders which were released from credit block, but I require the ID and Date (who released and when relaesed).
I hope my requirement is clear.
Thanks & Regards,
Sreehari.

Sales orders with credit issues taking availability stock

Hi,
I am doing confirmation using Global ATP in APO. The confirmation is well done, but the confirmed quantity for sales orders with clients that have credit issues is taken the available sotck for other sales orders with ok clients that I want to confirm the quantity they ordered.
For example:
Stock: 10 PC
Client A order 15 PC and 10 are confirmed, but the ordered is retained becuse of credit issues with client A.
Then client B order 3 PC, but nothing is confirmed because the ordered for client A is reserving the stock (note: this would be ok if client A had not credit issues).
So, I want that the 3 PC for client B are confirmed and the 10 PC not reserved for the cient A while client A has credit issues.
How could I configured, so that the orders with credit issues do not reserve stock for the incoming orders?
Thanks a lot.

Hi DB49,
thanks for the quick answer.
I checked the configuration in the R3 and seems to be fine. To prove it, I disconnect APO and did the availability check in the R3 system and it is working fine; the orders quantities that are blocked because of credit issues, do not reserve stock for incoming orders.........son new incoming orders are well confirmed.
But after connecting APO the problem continues. I checked the next points.
In R3 transaction CO09: takes to the APO screen and you see the ATP available quantity OK (do not consider the quantities of the credit issues orders). But at the moment that you make the order (VA01) it does not confirm any stock and if you select the line and go to the ATP screen (the same you get from the CO09) the quantities of credit issues orders are taken into account..the ATP availability quantity changes from the first going directly from the CO09.
What could it be?
Note: it was working fine with APO, I started to have the issue after implementing note 1262475 in APO. This note was becuase the BAPI_APOATP_CHECK was not brigning any value for the ATPQTY_***.
Thanks a lot!!!

Credit sales order with credit check without top up limit

Hi Experts,
I have a silly question, just wanted to confirm is this possible in SAP system?
I have check thru seem no such function.
My user requested a requirement is credit sales order with credit limit check however without top up credit limit to specific customer. eventually allow this specific customer sales order, delivery order without blocking and created succesfully?
Thanks & Regards,
Yong Kok Wah

Hi,
Use a seprate risk category for such customer. In OVA8 Setting for the given risk category set the Credit Limit Seasonal factor.
By means of above setting system will support the concept of TOP Up credit limit (for a given time period) for given customer against said credit limit.
Regards
Digambar Pandey

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
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.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

BAPI_SALESORDER_CREATEFROMDAT2 for Return Orders and Credit Orders

Dear experts,
I've been searching the SDN forums for information about the usage of BAPIs to create Sales Orders, Return Orders and Credit Memos. Unfortunately it seems hard to get consistent answers around the usage of BAPI_SALESORDER_CREATEFROMDAT2.
Is it, or is it not possible, to use BAPI_SALESORDER_CREATEFROMDAT2 to create Return Orders and Credit Memos with reference to other documents? Can someone please let me know if they have successfully implemented this scenario?
Many thanks and best regards,
Anna Englund

When you see the Code inside the BAPI BAPI_SALESORDER_CREATEFROMDAT2
CALL FUNCTION 'SD_SALESDOCUMENT_CREATE'
       EXPORTING
            SALESDOCUMENT           = salesdocumentin
            SALES_HEADER_IN         = ORDER_HEADER_IN
            SALES_HEADER_INX        = ORDER_HEADER_INX
            SENDER                  = SENDER
            BINARY_RELATIONSHIPTYPE = BINARY_RELATIONSHIPTYPE
            INT_NUMBER_ASSIGNMENT   = INT_NUMBER_ASSIGNMENT
            BEHAVE_WHEN_ERROR       = BEHAVE_WHEN_ERROR
            LOGIC_SWITCH            = LOGIC_SWITCH
            BUSINESS_OBJECT         = *'BUS2032'*
see it is only used for Sales Order(since BUS2032 is for sales order).
you need to create or copy the BAPI BAPI_SALESORDER_CREATEFROMDAT2 to custom Function.
then change the Business Object to BUS2094 (it is for Credit memo) . Reference i tried it didn't work that time. you check it once with the new Custom FM.

Down Payment processing for Sales orders using Milestone Billing Plan

Hi,
The business scenario is as follows.
The delivery for the sales orders are to be created only after the pre payment( a percentage of the total sales order value) is made by the customer.
Hence the sales orders while creation are blocked for delivery creation using credit block by means of a userexit.
The credit manager checks the blocked sales orders using VKM1 transaction and verify if there are any payments made by the customer to cover this pre payment to be made.
If it is enough to cover then he releases the sales order manually for delivery creation.This is a complex process since there are too many sales orders and the payments made by the customer may not match the amount to be paid(it can be greater or lesser).The customer just pays a huge amount which is to be distributed among the sales orders for pre payments.
Later, when the invoice is created, the customer account is cleared manually using F-32 transaction for the oldest open invoices.
Here again there is a huge manual effort involved since he need to distribute the amount against the invoices using oldest open item principle.
As a solution we are planning to implement "Down Payment processing for Sales orders using Milestone Billing Plan".
Is this the right solution?
Can you please give the steps in detail to implement this functionality for above scenario?
We are using SAP 4.7 version without Project Systems.
Thanks in advance.
Regards,
Ragesh

Hi Ragesh
Check the links where you will get the entire down-payment configuration
[https://forums.sdn.sap.com/post!replydownpayments ]
Regards
Srinath

How to list Sales Order with credit block

Hi, Gurus,
I really don't know how to list sales orders with credit block?
Is there any way for end user to do it?
If so, is it possible to list SO with credit block for certain period of time such as one month?
Any help would be appreciated.

HI
Check T-Code VKM2 (Released documents)
You need to check VKM1 (Blocked Documents)
Sorry before i gave wrong information , myself i corrected VKM2 for released not for blocked list (Due to non Availability of SAP access )
Regards,
Prasanna
Edited by: prasanna_sap on Feb 7, 2012 7:12 AM

Block return sales orders or credit notes?

Hi,
Could someone please explain how I block return sales orders or credit notes?
Also is there a way of searching which sales order documet types have been used for credit notes?
Thanks

Hi Friend,
The billing block is comming from the tx. VOV8 -> choose the Order type -> billing
block -> you could set billing block here.
In Shipping column, there is also a field Delivery block where you could set delivery
block for the order type.
Or you could also set delivery block and billing block manually when you create the order.
You could check order type which is used as return or credit memo request by following way:
SE16 -> TVAK -> use selection criteria VBTYP = H and K
H Returns
K Credit memo request
Then excecute, you could get the order type you want.
Best regards,
Alex

Check if the Sales Order is credit block.

Hello Everyone,
I have a requirement related to third party sales order and delivery. In the first system, a sales is created and then the PO gets created. Upon the creation of the PO a IDOC gets generated. The inbound IDOC in the other system triggers and a sales order gets created. The requirement is that if sales order in the first system is on credit block then automatically the sales order in the second system should go on delivery block.
The solution that I have thought is that when the IDOC gets created after PO generation there itself add a flag to IDOC in case of credit block in sales order. BUT HOW TO CHECK CREDIT BLOCK of the SALES ORDER IN THE CUSTOMER EXIT?
Any help is appreciable.

Hi Rahul,
Need some more clarification on why sales order is created in the second system, if it is a third party process ?
are you creating delivery from the corresponding sales order of second system to replenish sales order of first system ?
are you using standard IDOC type for creating Sales order from PO ?, if so check the Corresponding Function module which may have user exists
check Function module : IDOC_OUTPUT_ORDRSP
At first system, if the sales order is credit block you can restrict creation of PR-->PO in the first system itself, this is a standard Functionality
This would be easier than looking for user and coding in IDOC function module
try and revert
thanks
santosh

Copy control from Sales order to Credit memo-VTAA

Hi
We have a below requirement..
While copying from sales order to Credit memo order type,defualt payment terms in credit memo order type should be always change to NT00(payable immdtly due date)
So we had written a routine under sales order copying .VOFM-901
In VTAA we have set 901 instead of 101 under Copying requirements for transferring business data-under change header view..
But while creating sales order type CR with reference to normal sales order,it is not copying the NT00 payment term..
Can u tell us whether any other settings required in VTAA.
Note:We had copied existing 101 to 901 with addition logic -
IF VBAK-AUART = 'CR'.
VBKD-ZTERM = 'NT00'.
ENDIF.
Regards
Sudha

Hi Sudha,
The coding added in 101 is not enough to achieve your requirement, because of the fact that the VBKD-ZTERM will be filled again with the original value from CVBKD in the copy routine on the item level. (For example 102 for OR to OR in standard system)
Could you please create another routine 902(adding the addition coding to 102) and replace it on copy control for item level?
It should work then.
Regards,
Smile

Email for sales order on credit hold

Similar Messages

Maybe you are looking for