SALES BOM RETURNS PROCESS

Dear Friends,
I have recently created some SALES BOMS which carries out pricing and inventory at the component level (LUMF). i am now trying to carry out returns of some of these BOMs but have been getting problems doing so. one error is saying that the item category of the component material connot be determined.
can anyone explain if there is any standard way that SAP handles returns of SALES BOMS if it is allowed at all? Can the configuration steps be given to make this happen, i would like step by step instructions.

Hi,
during sales order
header : OR + LUMF -- TAP
item : OR + Norm + + TAP --- TAN
Config required during returns :
header : RE + LUMF -- should be having a returns item cat at VOV4.
item : RE + Norm+ + (one which you are going to determine above) --- (Component item cat at VOV4)
A product can be returned depending on the business terms and conditions whether its a BOM or a normal product. From a customers perspective its just a product he is buying and can be returned if there is a problem.
regards
sadhu kishore

Similar Messages

Addional lead time for Sales BOM kitting process

When a Sales Order BOM Sales Order is scheduled, we would like to have a lead time added for the Shipping kitting step. So the pick date will be X number of days before the ship date.
Is there a way to do this is ?
Thanks,
Doug Karien.

Hi DK,
Go to Ent structure > Definition > LE > Define shipping point, choose your shipping point, click on detailsand check there, "Rounding work days" filed may provide you some soln.
Regards
SD

Sales BoM - Drop Ship

Hi,
ist it possible to generate a sales BoM with a items from a drop ship stock?
Philipp

Philipp,
When the Sales BOM is processed, at the time of Delivery, it will need inventory for all child Items. The Drop ship Item will not have inventory and therefore you cannot have a dropship item in a Sales BOM.
If in Administration > System Initialization > Document Settings .....Block Negative Inventory is not checked then the Delivery could be processed but the Dropship Item would show as negative onhand quantity in Inventory.
This is not technically correct
Suda

Return process in Third Party Sales

Hi ppl need some help,
In Third party Sales what happens if certain goods supplied by the Vendor to the customer are 'Defective' & are to be returned by the customer.
Does the customer return it to the Company to which he placed the order or he returns it to the Vendor.
How can we configure this process in SAP to settle the billing & issue the credit memo to the customer?
Shilpi

Hi Shilpi,
third party Return process you can configure like this,
Take return goods from ur customer, Your customer will return goods to you and not to vendor, remember one thing ur cutomer doesnt know who is vendor.
Create CR with refeerence to RE. Because RE will contain that Product and quantity which you ar getting back from the Customer and that you have invoiced the customer.
E.G. If you Sent 2 Quantiy of Materail XYZ at 50 Rs each to the customer, but you Got invoice from ur vendor at 40 Rs Each.
and if customer retuirn 1 quantity u have to return him 50 Rs and not 40 Rs.
So Create CR with respect to RE.
Hope this will help.
Revert back if u need any further help.
Thanks,
Raja

Third Party Sales Returns process

Hello All
We have a third-party sales process which is automated i.e Sales order and Purchase requisitions(VA01) are created using the data coming in the incoming EDI file, the Purchase requisition is automatically converted to a Purchase order, the Invoice Reciept(MIRO) is posted and the Sales Invoice (VF01) is posted.
The question is how do we handle the Returns or the Credit process?
Is there a way I can configure the system to create a Returns order which will also update the Pur.Req quantity then the Purchase order quantity or directly the Purchase order quantity. I can then use this information to raise a credit to the Vendor Invoice.
I don't want to just raise a credit memo and update the sales side and leave the purchase side open.
I appreciate your reply.
Best Regards
Rama

Third Party Return Process
Please check this extract from the sap library :
If the vendor grants you a credit memo on a quantity or a value basis, you can then send this credit memo directly to your customer.
The billing type Third-party credit memo (G2S) is available for this. The billing type Third-party credit memo works with the item category TASG (third-party credit memo item). The Billing-relevance indicator F is set in Customizing for Sales for this item category. This means that the cost is not created. In Customizing for Sales, the item category TASG is set at item level in copying control for the billing type G2S (copying control sales document by billing document) as the target item category (source: TAS-> Target:> TASG.)
Process Flow
Create a billing documente with billing type Third-party credit memo (for further information, see the section Creating a billing document in the Billing document). Enter the third-party order as a document still to be processed. The quantities are automatically removed from the invoice.
The above is the process for giving a credit memo which can be adapted for return goods.
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Third party Sales Return Process

Hi..
Can anybody just guide me about Thrid Party Sales Return Process?
My Mail Id is [email protected]..Could you please send me steps and confign guidelines...
Regds
Manoj

Dear Manoj Mahajan,
The return process is not supported by standard SAP.
Considering my experience even if you want to get it done through some cutomizations it is not very successful.
Please refer to SAP note 751609 which will give the further details
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

Letter of Credit in Sales return process/

Hi All,
This issue is related to Letter of Credit, I created a sales order and maintained Financial document in Billing Tab (Letter of Credit) & saved the sales order and the balance of LOC is updated, i created Delivery & Invoice also . Later stage the customer returned the materials and we Created the return sales order but the letter of Credit open value is not increasing or not Crediting.
Please let us know in case of return process weather the LOC or Financial document will credit or not?
Regards

Hi
Letter of Credit is used in credit management as one of the tool for Risk management. In case of return process LOC or financial document wont get credited as LOC is for intimation to the customer if the risk level has come to high.Also run the t.code VXDG.
Please check the below link which may help you
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDFTLOC/SDFTLOC.pdf
Regards
Srinath

What is the purpose of using return process sales doc type?

what is the purpose of using return process sales doc type?

hi,
There is the standard process
1)Order type( RE) VA01
2)Delivery( LR)Vl01n with reference to return order
i)if the movement is 651then system will not generate accounting document upon doing Post goods Receipt ,the stock will be in the return location
then you use movement type 453 to get the stock in UN restricted
ii)if the movement type 653 the system generates accounting document and stock posts in unrestricted use
3)With reference to Delivery raise Credit memo (RE) with transaction VF01
CHAN

Sales Return Process-Invoice(Credit Memo) with ref. to delivery

Dear All,
I am doing sales return process.
Sales Order-RE
Delivery-LR
Invoice-RE,
with ref. to sales order it is allowing me to create invoice.
But,with ref. to delivery it is not allowing.
It is giving "The document is not relevant for billing".
I have changed item category REN for delivery (A) related billing.
Also changed req. copy control setting.
Can anybody guide on this issue.
Best Regards
Sainath

Hello,
Normally return credit memo will be generated with reference to the retrun order, and that is the standard SAP process. Do you have any specific requirements to have the credit memo with reference to a retrun delivery?
The Item category REN Billing Relevence will be B as per SAP standard, if you wish to have a delivery related credit RE, the make this to A .
Maintain the Delivery to Billing Copying control in VTFL for LR --> RE, add the item categroy REN.
Maintain the copying requirements for header as 3 Header Del Rel and for item as 4 Deliv-Related item .
Once these setting are done, then check whether the RE billing type is triggering from LR?
Prase

Sales Return Process in Excise

Hi,
Can any one explain me the Sales Return Process with Excise Details.
How to deal with excise when sales are return from customer.
Please explain me if customer returns complete material what will be the process.
In case if customer Returns partial quantity how to process
How will be the excise implications.
Can u please explain me the above 2 process.
Thanks.

Please make a search in the forum as this question has been answered many times. Check some of those threads
[Excise return in Sales Return   |Excise return in Sales Return]
[Sales return delivery process wtih Excise   |Sales return delivery process wtih Excise]
[return in excise   |return in excise]
[Excise Return   |Excise Return]
[Excise Invoice Selection in Return Delivery   |Excise Invoice Selection in Return Delivery]
thanks
G. Lakshmipathi

Depo sales returns process

*STO process*
ME21n : UB sto with Delivery
Me29n : release the PO
Vl10b NL---Item NLN
Vl02n
Vf01 u2013JEX-Proforma
J1iin
Goods reeipt :MIGO _outbound delivery Excise number and Excise date
J1idepotstock1
Depo sales
Va01: Zdep
Vl01n
J1ij: caputure the Excise duties
Vf01: Capture the Excise duties (Routine: 356)
upto this OK
Now my cleint wants Depo return process
Step 1: Va01 reference to Billling here basic excise duty JEXP is coming right and JECS and JHCS is not flowing it is taking JEXP duty only.
Step 2:Vl01n
Step 3 :Vf01 :Order-related credit mem- here Excise duties are coming but it is taking the 8 % 2 % and 1% it should take from depo sales return order step 1
Step 4: J1ih -Depo plant and Depo excise group JV adjustment by using additional excise button.
Please let me know where i have done the mistake , i have check in copy control it is maintain Pricing type: " D"
G. Lakshmipathi posted
1 Create a return order in Depot
2 Key in the invoice number and execute
3 Assign Order Reason and save
4 Create a return delivery and do PGR. Maintain storage location 0005
5 Create Transfer posting in MB1B with movement type 453, storage location 0005 and save
6 Note down the material document reference
7 Go to J1IG to reverse excise issue posting
8 Click "Capture"
9 Key in the material document number and series group
10 Click "Details". Now select the line item and again click "More documents"
11 Key in the original excise invoice reference created at supplying plant
12 Skip all warning message and go back
this i am checking if i take this solution
For Depo returns Va01 reference to Billling here basic excise duty JEXP is coming right and JECS and JHCS is not flowing it is taking JEXP duty only._* where is the missing setting i have not done.
and For Billing output :Vf01 :Order-related credit mem- here Excise duties are coming but it is taking the 8 % 2 % and 1% it should take from depo sales return order step 1
Edited by: balashowry raju on Apr 23, 2010 9:03 AM

solved but in depo returns credit memo here still excise values are not copying from depo returns sales order.
where the problem lays i have checked VTFA copy control and sap notes .
still exploreing going on

Drop Ship processing for Sales BOM

Hi,
We have a requirement to have a Sales BOM drop shipped from a Vendor. Only the header material is relevant for pricing and purchase order. However, we have a business requirement to explode the sales BOM in the sales document and billing document to address statistical pricing requirements at the component level.
Since only the header material is required in the PO, it has a billing relevance of 'F'. However, we have set the components to be relevant for order related billing. Standard SAP opens up the components for billing even though a vendor invoice for the header has not been received.
Can copy control be used to control the components from being billed unless the header is billed AND the quantity of component materials modified based on the header material being invoiced ? Is it possible to only explode the sales BOM in the billing document using a billing document exit ?
Would appreciate suggestions from the forum.
Regards

Hi
The billing document creation can be controlled through the copying requirement in Copy Control of Billing documents.
Transaction VOFM | Billing documents: Create a new requirement which prevents billing unless the parent item has the vendor invoice receipt.
This requirement has to be then assigned to the respective billing and sales document type in copy control.
Regards,
Vinu

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

Return process of componets of finished goods

Hi
Can u pls guide for return process of componets of finished goods
Sales order & invoice contains only finished good material code(e.g Panel).
We want to take return of componets assembled in that panel.
Can it be done by regular return order process.

Hi,
I think you may have to use CS-Module, where there is a process called "Returns and Repair order processing."
Please ref. the link below.
http://help.sap.com/saphelp_46c/helpdata/en/e6/4a903f9e0311d189b70000e829fbbd/frameset.htm
It can be done in the following way
Please maintain BOM for the Camponents, under the main material.
You can do it either using "CS01" or under the menu path:
Logistice > Customer Service > Maintain Technical Objects > BOM > Equipment BOM or Material BOM.
Hope this will be of good help to you,
Regards
DSR
Edited by: D.Srinivasa Rao on Nov 24, 2011 6:42 AM

BOM Returns values are not getting copied

Dear All,
Sales Order with Sales BOM, header item will be delivered and the line items are order related billing, the requirement is returns for the same, the BOM is exploring in the return order but we need the same Pricing(inclu all taxes) is copied to Return Order Type. Sales order to sales orders are the copy controls (VTAA), we have tried with copying requirements, pricing type A, B, D, G, it is not updating the conditions and value of the sales order,
The returns order process is with reference to Sales Order
Kindly guide me to resolve the issue
Regards,
Mani,

Hi Mani,
we have tried with copying requirements, pricing type A, B, D, G, it is not updating the conditions and value of the sales order,
From above statment it seems that you have different pricing procedure. If this is the case make sure that you have same conditions in pricing procedure (and hope you have not restricted price calculations based on sales document type, item category etc which will differ in both documents)
You can set the pricing type as G and modify the tax condition for proposing the pricing date to document pricing date(can try option of B or D not sure)
Please try and revert back to forum if you have any issues.
Thanks and Regards,
Atul

SALES BOM RETURNS PROCESS

Similar Messages

Maybe you are looking for