Customer sales return and same material return to respective vendor

Hi Experts
would like to get your valuable inputs in the below mention scenario
I procured material ABC qty 10 from vendor and same has been sale to customer
now Customer is returned the material ABC qty 5 to my client
now client want to return the goods for the respective vendor from whom it was procured.
The requirement is the system should able to predict automatically from whom the goods has been procured?
note:- client can procure the same material ABC from 10 different vendor
Is there any common link can be maintained between purchase material from vendor to my client and from my client to customer ?

Hi,
Lets Try to do in this way,
1.Create a sales order
2. Create a PO for that material, Now at GR in delivery filed give the sales order number. so in PO histry tab of PO we can c the sales order number. and sales return can link with PO.
Now in case Sales order is latter the Purchase then
in Sales order PO filed we can give the PO number on which we have procurred the material. so when u go to sales order display system will give PO ref.
3. Now while sales return you will get the ref. of sales order
4. Lastly it is time to send the material to the vendor 4m whom it is been purchased, here u can get the link :- 4m sales order, PO field u'll get or 4m PO history you can get the sales order number.
try this mix, it may work without any further efforts
Rgds
S

Similar Messages

Single planned order for different sales order of same material

hi frnds
my client want that if there is two or more sales order of same material in a specific period than he require single planned order during mrp run for that material or when if he enter same material in two different line in single sales order than mrp doesnt considered it line item aand produce single planned order for both sales order
please help me out its very urgent
thanks

Hi,
In Mrp 3 view set the availability check as 01 and in Mrp 1 view
Keep the lot size as periodic lot size and try the same.
Thanks,
S.Nandhakumar

Scenario of Import P.O from same material get money from vendor and custome

Hi Experts,
My client is procuring certain material Quantity 10 by Import, As when he recieve the 10 Quantity material he founds 8 Quantity is to be Okay and the other 2 founds to be damaged, As it is import material he cannot return it to import vendor, in this situation he takes the photocopy of the 2 damaged material and get debits from vendor without actual returning to import vendor apart from this the damaged goods he sells for lower price.
So from the same material he gets the money double time one from Vendor and other from Customer.
How to MAP this Scenario in SAP ?
Plaese advice.
Best Regards
Javeed Ahamed

Hi Javeed,
Are u using QM module? If u are using, u can activate quality inspection for this material. You can do 101 movement for total qty i.e. 10 nos.
Then in usage decision, you can accept 8 nos and reject and scrap 2 nos.
If u are not using QM module, u can still post 101 movement for 10 numbers. Then you can screap 2 nos with movement type 551.
Hope this will resolve ur problem.
Award points if found useful

Excisable and Non Excisable plants for the same customer and same material

Hi All,
We have a customer who purchases the SAME goods from two different plants, one plant is Excisable and another plant is Non Excisable. So sales area of the customer is same for both the plants. When customer buys from Excisable plant Excise Duties should applicable and when the same customer buys from Non Excisable plant Excise Duties should not be applicable. If I maintain the Excise indicator as 1 in customer's J1ID then Excise Duties are applicable for the customer from wherever he buys the goods.(If he buys the goods from Excisable and Non Excisable plants Excise Duties are flowing).
So, my query is: if the customer buys from non-Excisable plant, Excise Duties should not flow.
So I am planning to create a new sales org for Non Excisable plant, then the sales area of the customer will change.
Is there any other way to over come this issue? Plz guide me.
Thanx&Regards,
RAMU

Dear Ramu
My suggestion is creating a new sales organization is not required just to fulfill this excise requirement.
Let us assume you have two plants
- 1000 is excisable and
- 2000 is non excisable
for material ABC
Now go to J1ID, select the tab "Material and Chapter ID combination" and maintain the excise tax indicator for plant 1000 only.
By doing so, while creating sale order, you input the delivering plant and based on the settings you maintained in J1ID, excise duty will be determined in that sale order.
thanks
G. Lakshmipathi

My lov returns AND displays the return value

Hi,
For 1 of the columns I'm representing in APEX, I choose 'Display as text, based on a lov'. I'm using:
select aan.id||', '||r.naam||', '||a.woonplaats d, aan.id r
from wmo_aanvragen aan
, wmo_dossiers d
, wmo_relaties r
, wmo_adressen a
where d.avg_1_id = aan.id
and d.rel_nummer = r.nummer
and a.rel_nummer = r.nummer
and a.id = (select min(e.id) from wmo_adressen e where e.REL_NUMMER = r.nummer
and e.EIND_DATUM is null)
and d.id = (select min(f.id) from wmo_dossiers f where f.AVG_1_ID = aan.id)
But somehow it returns AND displays the 'aan.id' value instead of displaying the display value. Does anyone know howcome?? In TOAD it works fine. Starting a new page also doesn't make any sense
Niels

Nope, doesn't work either.
I've an identical statement which does work...
select z.id||', '||zst.omschrijving||', '||r.naam||', '||a.woonplaats d, z.id r
from wmo_zorgverleners z
, wmo_zorgverlener_soorten zst
, wmo_relaties r
, wmo_adressen a
where z.zst_id = zst.id
and z.rel_nummer = r.nummer
and a.rel_nummer = r.nummer
and a.id = (select min(e.id)
from wmo_adressen e
where e.REL_NUMMER = r.nummer
and e.EIND_DATUM is null)
Here,iIt does display the contcatenated text..

STO returns and visibility of qty at plant vendor in MD04

Hi Guru's,
When I create a return STO in R/3 the requirement appears at the receiving plant in MD04 but no receipt appears at the supplying plant (it is a return so opposite to normal). When I create a delivery for this STO nothing changes in the MD04 view at receiving or supplying plant.
We would like to see the return and the return delivery as a receipt in MD04 so it it contributes to available qty. Can you provide some ideas on how this could be done?
Thanks
Andrew

Hi,
I have similar problem for our client. Can you explain me how to you resolved the issue?
Thanks,
Muthu

Sales Order and obligatory material's parameter fields - help!!!

Hi,
My problem is:
I've got to create material in MM by using BAPI_MATERIAL_SAVEDATA, so that this material can be later used as an item in Sales Order (SD). Do you know what parameter fields from which structures are obligatory in my case? I've already passed quite a lot of data to this BAPI, but I still get following error:
"Material myMaterial is not defined for sales org. 4000, distr.chan. 01, language FI"
Any suggestion will be appreciated and properly rewarded if useful.
My Java source-code is available below. Check this out and let me know what is missed.
                * HEADDATA FOR BASIC VIEW
               Structure headData = input.getStructure("HEADDATA");
               headData.setValue(_material, "MATERIAL");
               headData.setValue("1", "IND_SECTOR");
               headData.setValue(_matl_type, "MATL_TYPE");
               headData.setValue("X", "BASIC_VIEW");
               headData.setValue("X", "SALES_VIEW");
               //headData.setValue("X", "MRP_VIEW");
               headData.setValue("E", "INP_FLD_CHECK");
                * CLIENTDATAX FOR BASIC VIEW
               Structure clientDatax = input.getStructure("CLIENTDATAX");
               clientDatax.setValue("X", "MATL_GROUP");
               clientDatax.setValue("X", "OLD_MAT_NO");
               // clientdatax.setValue("X", "PROD_HIER");
               clientDatax.setValue("X", "BASE_UOM_ISO");
               clientDatax.setValue("X", "NET_WEIGHT");
               clientDatax.setValue("X", "UNIT_OF_WT_ISO");
               clientDatax.setValue("X", "ITEM_CAT");
               clientDatax.setValue("X", "PUR_VALKEY");
               clientDatax.setValue("X", "LABEL_TYPE");
               clientDatax.setValue("X", "LABEL_FORM");
               clientDatax.setValue("X", "DIVISION");
                * CLIENTDATA FOR BASIC VIEW
               Structure clientData = input.getStructure("CLIENTDATA");
               clientData.setValue("02", "MATL_GROUP");
               clientData.setValue("testmaterial", "OLD_MAT_NO");
               // clientdata.setValue("1000000790","PROD_HIER");
               clientData.setValue("PCE", "BASE_UOM_ISO");
               clientData.setValue(0.111, "NET_WEIGHT");
               clientData.setValue("KGM", "UNIT_OF_WT_ISO");
               clientData.setValue("NORM", "ITEM_CAT");
               clientData.setValue("UV03", "PUR_VALKEY");
               clientData.setValue("1", "LABEL_TYPE");
               clientData.setValue("E1", "LABEL_FORM");
               clientData.setValue("01", "DIVISION");
                * SALESDATAX
               Structure salesDatax = input.getStructure("SALESDATAX");
               salesDatax.setValue("4000","SALES_ORG");
               salesDatax.setValue("01","DISTR_CHAN");
               salesDatax.setValue("X","ITEM_CAT");
               salesDatax.setValue("X","DELYG_PLNT");
                * SALESDATA
               Structure salesData = input.getStructure("SALESDATA");
               salesData.setValue("4000","SALES_ORG");
               salesData.setValue("01","DISTR_CHAN");
               salesData.setValue("NORM","ITEM_CAT");
               salesData.setValue("4200","DELYG_PLNT");
                * PLANTDATAX
               Structure plantDatax = input.getStructure("PLANTDATAX");
               plantDatax.setValue("4200", "PLANT");
               plantDatax.setValue("X", "MRP_TYPE");
               plantDatax.setValue("X", "MRP_CTRLER");
               plantDatax.setValue("X", "REORDER_PT");
               plantDatax.setValue("X", "MINLOTSIZE");
               plantDatax.setValue("X", "LOADINGGRP");
                * PLANTDATA
               Structure plantData = input.getStructure("PLANTDATA");
               plantData.setValue("4200", "PLANT");
               plantData.setValue("ND", "MRP_TYPE");
               plantData.setValue("001", "MRP_CTRLER");
               plantData.setValue("0", "REORDER_PT");
               plantData.setValue("100", "MINLOTSIZE");
               plantData.setValue("0001", "LOADINGGRP");
                * MATERIALDESCRIPTION EN
               Table materialDesc = tables.getTable("MATERIALDESCRIPTION");
               materialDesc.appendRow();
               materialDesc.setValue("ENGLISH", "LANGU");
               materialDesc.setValue("EN", "LANGU_ISO");
               materialDesc.setValue(_material+" - test for sales order", "MATL_DESC");
                * MATERIALDESCRIPTION FI
               materialDesc.appendRow();
               materialDesc.setValue("FINNISH", "LANGU");
               materialDesc.setValue("FI", "LANGU_ISO");
               materialDesc.setValue(_material+" - test FI", "MATL_DESC");
               // materialdesc.insertRow(0);
               // MeasureX
               Table measurex = tables.getTable("UNITSOFMEASUREX");
               measurex.appendRow();
               measurex.setValue("X", "ALT_UNIT_ISO");
               measurex.setValue("X", "UNIT_DIM_ISO");
               measurex.setValue("X", "LENGTH");
               measurex.setValue("X", "WIDTH");
               measurex.setValue("X", "HEIGHT");
               measurex.setValue("X", "VOLUME");
               measurex.setValue("X", "VOLUMEUNIT_ISO");
               measurex.setValue("X", "GROSS_WT");
               measurex.setValue("X", "UNIT_OF_WT");
               measurex.setValue("X", "UNIT_OF_WT_ISO");
               // measurex.insertRow(0);
               // Measure
               Table measure = tables.getTable("UNITSOFMEASURE");
               measure.appendRow();
               measure.setValue("PCE", "ALT_UNIT_ISO");
               // measure.setValue("X","DEL_FLAG");
               measure.setValue("CMT", "UNIT_DIM_ISO");
               measure.setValue(0.111, "LENGTH");
               measure.setValue(0.111, "WIDTH");
               measure.setValue(0.111, "HEIGHT");
               measure.setValue(0.3, "VOLUME");
               measure.setValue("CMQ", "VOLUMEUNIT_ISO");
               measure.setValue(0.111, "GROSS_WT");
               measure.setValue("KGM", "UNIT_OF_WT");
               measure.setValue("KG", "UNIT_OF_WT_ISO");
               //Tax classifications
               Table tax = tables.getTable("TAXCLASSIFICATIONS");
               tax.appendRow();
               tax.setValue("FI", "DEPCOUNTRY");
               tax.setValue("FI", "DEPCOUNTRY_ISO");
               tax.setValue("MWST", "TAX_TYPE_1");
               tax.setValue("1", "TAXCLASS_1");
               //tax.setValue("01", "TAX_IND");
               tax.appendRow();
               tax.setValue("EN", "DEPCOUNTRY");
               tax.setValue("EN", "DEPCOUNTRY_ISO");
               tax.setValue("MWST", "TAX_TYPE_1");
               tax.setValue("2", "TAXCLASS_1");

Hi Alistair,
I have a full access to SAP, so I can create and extend material whenever I want through MM01/MM02, but my target is to develop a method in Java, which creates a fully functional material to be used later in Sales Order.
A code listed in my prevoius post shows most of my method. I've got to indicate that my method works correctly and creates material. I've checked it through MM03 - I mean my material created with my method exists.
Moreover both sales org. and distr. channel are passed to BAPI, as you may see in the following code:
                * SALESDATA
               Structure salesData = input.getStructure("SALESDATA");
               salesData.setValue("4000","SALES_ORG");
               salesData.setValue("01","DISTR_CHAN");
               salesData.setValue("NORM","ITEM_CAT");
               salesData.setValue("4200","DELYG_PLNT");
But the problem occurs when I wanna create Sales Order (VA01) and when I choose the item. Material created by my method causes error:
"Material myMaterial is not defined for sales org. 4000, distr.chan. 01, language FI"
I don't understand why? I'm not SAP specialist, but in my opinion I've passed necessary data.
Do you any idea?
Thanks in advance. Every helpful suggestion will be properly rewarded.
BR,
Rafal

Sales Order and obligatory material's parameter fields

Hi,
My problem is:
I've got to create material in MM by using BAPI_MATERIAL_SAVEDATA, so that this material can be later used as an item in Sales Order. Do you know what parameter fields from which structures are obligatory in my case? I've already passed quite a lot of data to this BAPI, but I still get following error:
"Material myMaterial is not defined for sales org. 4000, distr.chan. 01, language FI"
Any suggestion will be appreciated and properly rewarded if useful.
My Java source-code is available below. Check this out and let me know what is missed.
                * HEADDATA FOR BASIC VIEW
               Structure headData = input.getStructure("HEADDATA");
               headData.setValue(_material, "MATERIAL");
               headData.setValue("1", "IND_SECTOR");
               headData.setValue(_matl_type, "MATL_TYPE");
               headData.setValue("X", "BASIC_VIEW");
               headData.setValue("X", "SALES_VIEW");
               //headData.setValue("X", "MRP_VIEW");
               headData.setValue("E", "INP_FLD_CHECK");
                * CLIENTDATAX FOR BASIC VIEW
               Structure clientDatax = input.getStructure("CLIENTDATAX");
               clientDatax.setValue("X", "MATL_GROUP");
               clientDatax.setValue("X", "OLD_MAT_NO");
               // clientdatax.setValue("X", "PROD_HIER");
               clientDatax.setValue("X", "BASE_UOM_ISO");
               clientDatax.setValue("X", "NET_WEIGHT");
               clientDatax.setValue("X", "UNIT_OF_WT_ISO");
               clientDatax.setValue("X", "ITEM_CAT");
               clientDatax.setValue("X", "PUR_VALKEY");
               clientDatax.setValue("X", "LABEL_TYPE");
               clientDatax.setValue("X", "LABEL_FORM");
               clientDatax.setValue("X", "DIVISION");
                * CLIENTDATA FOR BASIC VIEW
               Structure clientData = input.getStructure("CLIENTDATA");
               clientData.setValue("02", "MATL_GROUP");
               clientData.setValue("testmaterial", "OLD_MAT_NO");
               // clientdata.setValue("1000000790","PROD_HIER");
               clientData.setValue("PCE", "BASE_UOM_ISO");
               clientData.setValue(0.111, "NET_WEIGHT");
               clientData.setValue("KGM", "UNIT_OF_WT_ISO");
               clientData.setValue("NORM", "ITEM_CAT");
               clientData.setValue("UV03", "PUR_VALKEY");
               clientData.setValue("1", "LABEL_TYPE");
               clientData.setValue("E1", "LABEL_FORM");
               clientData.setValue("01", "DIVISION");
                * SALESDATAX
               Structure salesDatax = input.getStructure("SALESDATAX");
               salesDatax.setValue("4000","SALES_ORG");
               salesDatax.setValue("01","DISTR_CHAN");
               salesDatax.setValue("X","ITEM_CAT");
               salesDatax.setValue("X","DELYG_PLNT");
                * SALESDATA
               Structure salesData = input.getStructure("SALESDATA");
               salesData.setValue("4000","SALES_ORG");
               salesData.setValue("01","DISTR_CHAN");
               salesData.setValue("NORM","ITEM_CAT");
               salesData.setValue("4200","DELYG_PLNT");
                * PLANTDATAX
               Structure plantDatax = input.getStructure("PLANTDATAX");
               plantDatax.setValue("4200", "PLANT");
               plantDatax.setValue("X", "MRP_TYPE");
               plantDatax.setValue("X", "MRP_CTRLER");
               plantDatax.setValue("X", "REORDER_PT");
               plantDatax.setValue("X", "MINLOTSIZE");
               plantDatax.setValue("X", "LOADINGGRP");
                * PLANTDATA
               Structure plantData = input.getStructure("PLANTDATA");
               plantData.setValue("4200", "PLANT");
               plantData.setValue("ND", "MRP_TYPE");
               plantData.setValue("001", "MRP_CTRLER");
               plantData.setValue("0", "REORDER_PT");
               plantData.setValue("100", "MINLOTSIZE");
               plantData.setValue("0001", "LOADINGGRP");
                * MATERIALDESCRIPTION EN
               Table materialDesc = tables.getTable("MATERIALDESCRIPTION");
               materialDesc.appendRow();
               materialDesc.setValue("ENGLISH", "LANGU");
               materialDesc.setValue("EN", "LANGU_ISO");
               materialDesc.setValue(_material+" - test for sales order", "MATL_DESC");
                * MATERIALDESCRIPTION FI
               materialDesc.appendRow();
               materialDesc.setValue("FINNISH", "LANGU");
               materialDesc.setValue("FI", "LANGU_ISO");
               materialDesc.setValue(_material+" - test FI", "MATL_DESC");
               // materialdesc.insertRow(0);
               // MeasureX
               Table measurex = tables.getTable("UNITSOFMEASUREX");
               measurex.appendRow();
               measurex.setValue("X", "ALT_UNIT_ISO");
               measurex.setValue("X", "UNIT_DIM_ISO");
               measurex.setValue("X", "LENGTH");
               measurex.setValue("X", "WIDTH");
               measurex.setValue("X", "HEIGHT");
               measurex.setValue("X", "VOLUME");
               measurex.setValue("X", "VOLUMEUNIT_ISO");
               measurex.setValue("X", "GROSS_WT");
               measurex.setValue("X", "UNIT_OF_WT");
               measurex.setValue("X", "UNIT_OF_WT_ISO");
               // measurex.insertRow(0);
               // Measure
               Table measure = tables.getTable("UNITSOFMEASURE");
               measure.appendRow();
               measure.setValue("PCE", "ALT_UNIT_ISO");
               // measure.setValue("X","DEL_FLAG");
               measure.setValue("CMT", "UNIT_DIM_ISO");
               measure.setValue(0.111, "LENGTH");
               measure.setValue(0.111, "WIDTH");
               measure.setValue(0.111, "HEIGHT");
               measure.setValue(0.3, "VOLUME");
               measure.setValue("CMQ", "VOLUMEUNIT_ISO");
               measure.setValue(0.111, "GROSS_WT");
               measure.setValue("KGM", "UNIT_OF_WT");
               measure.setValue("KG", "UNIT_OF_WT_ISO");
               //Tax classifications
               Table tax = tables.getTable("TAXCLASSIFICATIONS");
               tax.appendRow();
               tax.setValue("FI", "DEPCOUNTRY");
               tax.setValue("FI", "DEPCOUNTRY_ISO");
               tax.setValue("MWST", "TAX_TYPE_1");
               tax.setValue("1", "TAXCLASS_1");
               //tax.setValue("01", "TAX_IND");
               tax.appendRow();
               tax.setValue("EN", "DEPCOUNTRY");
               tax.setValue("EN", "DEPCOUNTRY_ISO");
               tax.setValue("MWST", "TAX_TYPE_1");
               tax.setValue("2", "TAXCLASS_1");

I forgot to indicate sth important what actually might be read from my source code. Both sales org. and distr. channel are passed to BAPI to structure SALESDATA. Why SAP doesn't recognize it? Do you know any explanation? or somebody else?
                * SALESDATA
               Structure salesData = input.getStructure("SALESDATA");
               salesData.setValue("4000","SALES_ORG");
               salesData.setValue("01","DISTR_CHAN");
               salesData.setValue("NORM","ITEM_CAT");
               salesData.setValue("4200","DELYG_PLNT");

Line item wise exchange rate in sales order and same in billing

Hi,
The client requirement is that to have different exchange rate at line item level in sales order, for multiple sales order, we have different exchange rate in the line items wise, we do the collective billing through VF04. System is picking in the billing document, but not in the accounting document.
The accounting entry should be posted separate exchange rate wise. How to map the same.
Can anyone throw light on this issue.?
Regards,
Satya

Go through this thread
Difference in Billing Exchange rate(VBRP-KURSK) w.r.t OB08
G. Lakshmipathi

[10g] OE schema - Matching Customer Sales Rep And the ORDERS table

Hi,
I have this query:
select c.account_mgr_id, o.sales_rep_id, c.*, 'o', o.*
from customers c,
orders o
where c.account_mgr_id = o.sales_rep_id
But I can't find which salesman places the order.
It looks like there is a hierarchy in the Sales Department, the Account Manager and the Sales Representative?
Am I missing another table from the OE schema?
Many thanks for your help.
Edited by: JeanParis on Nov 28, 2010 11:50 AM

SQL> select c.account_mgr_id, o.sales_rep_id, c., 'o', o.
2 from customers c,
3 orders o
4 where c.account_mgr_id = o.sales_rep_id;
select c.account_mgr_id, o.sales_rep_id, c., 'o', o.
ERROR at line 1:
ORA-01747: invalid user.table.column, table.column, or column specificationBut with respect to your question ... why do you believe the information is present?
In what table? In what column(s)?

Canadian tax determination on basis of material group, Sales Office and...

...Customer region.
Hi,
We have a unique requirement for taxation in Canada. The constraints/requirements are:
1. For all customer located in the province Quebec (KNA1-REGIO = QC), if:
(a) the Sales Office on customer master (KNVV-VKBUR) not equal to QC (Quebec - user defined) and material group (MARA-MATKL) = 'X' or 'Y', we need the GST and QST to be charged
(b) for all other material groups, if the Sales Office on customer master (KNVV-VKBUR) not equal to QC (Quebec - user defined) we need only the GST to be charged (not QST)
How can this be achieved? We can explore the use of any other field too, apart from KNVV-VKBUR if it helps or even some kind of indicator on the customer master...
Appreciate any clues...can the material pricing group be of any use here? If so, how?
Thanks a lot.

Thanks, Nageshwar, I certainly don't want to complicate it with 2 condition types and prefer a requirement. However, in the requirement, I see an issue - since the taxes are determined on the basis of the ship to party (and we do have customers with out of QC but with their ship tos in QC and vice versa), the partner determination at the time of applying the pricing (i..e. VA01) has not yet taken place - not stored in any table...how do I get the system to understand the REGIO from the address data for the P. fn = WE (or SH)? How will the requirement get triggered if the system can't determine what the REGIO is? We need it to be applicable only if the REGIO is QC, not for others. Sales office and the material group are not a problem to ascertain. The REGIO is not stored in VBAK or VBAP and the VBPA entries are not yet done (at the time of VA01)...I can think of getting it only from KNA1 but am not sure how to.....any ideas?
Thanks!

Find Item number based on Sales document and material in GTS system

Dear experts,
I have a situation where in I created a Sales order in ECC system and transmitted the document to GTS for compliance check.
Now, during my subsequent processing in ECC side, there is a situation where in I need to check if the document (at every item level) is blocked for any reason or is it good to go. But I do not have the item number in ECC side (at the point where I'm calling RFC to GTS to check). I only have sales order number and the material number.
So, can some one point me table level information in GTS side on how I could find the item number based on Sales document and the material (In our scenario all our materials in a sales order will be distinct).
Please provide me table information on where the sales document number, item number, material info are stored in GTS.
Thanks for your time
-Amit

Use these tables
/SAPSLL/CORREF
/SAPSLL/PNTPR
/SAPSLL/CUIT

Material Return/Scrap Material from production generate inspection lot

Hi experts,
I would like to confirg the following:
When material return or scrapped material return from production(mvnt type 262), system is required to generate inspection lot.
How can I config this scenario?
Thanks!
Regards,
Daniel

The inspection lot origin '05' is assigned to movement type '262'.
(You can check this in update control at transaction OMJJ.)
So you have to activate the inspection type '05' or new one.
But you should be 'careful' because an inspection lot will be create even if other movement like '501'.
Regards
Luke

Difference between LIKP-VBTYP 'Returns' and 'Returns delivery for order'

Hi...I have tried researching this myself, but still can't seem to get a good answer. In the LIKP table, there is a VBTYP of 'H' for returns and 'T' for returns on delivery order. I am trying to understand the difference between the two...how could you have a return with it NOT being on a delivered order? Is there something basic I am missing? Any and all help extremely apprecated.

Hi,
I fully agree with the input given by Mr G Lakshmipathi.
VBTYP as field description implies, it just says about the SD document category , but applicable to all documents such as order(includes outling agreements, inquiry,quotation as well) , delivery , billing.
These values are inbuilt. wrt: document behaviour we use this doc category.
You can even observe, doc category: K & O -
K = Credit memo request which applicables only in VA01
O = Credit memo applicables only in VF01.
if you try to execute the table LIKP ( from SE16) with VBTYP=H, you will not get any doc's
I hope it adds info.
Regards,
Reazuddin MD

In subcontracting process same material to come back from vendor how?

hi
in subcontracting process i want to send x material for processing purpose and same material is going to come back tell me the process how can i do
chandra

hii
For ur scenario, u have carried out external service management process.
Because , subcontracting is nothing but , u have to X material and receivea as A materia or some different material.
SO if u r going to receive the same material , u can do it as service process.
Thanks
SAP-MM

Customer sales return and same material return to respective vendor

Similar Messages

Maybe you are looking for