PR & RFQ QTY MISMATCH

Hi
PR QTY is 10nos & RFQ is created with respect to PR.But system allows to create RFQ Higher than the PR qty.
Regards
Umapathy.M

hi,
You can create a RFQ for more qty than in the PR. it will allow
It is Standard SAP .
RFQ is only for reference purpose. Final you can correct the qty in the PR.
PR qty is final qty from which P.O is created
I have tried it is working
Regards
G.Ganesh Kumar

Similar Messages

Order qty and confirmed qty mismatch

Dear friends,
My requirement is System should not allow to go further if the sale order qty and confirmed qty(after avaialbility check) mismatch is there.Pls suggest.
Now currently system will check the availability qty and will show the information of confirmed qty in the another screen.and if we say continue the process, we can go ahead and save the document.but the document will be in open state.
So pls suggest the way i can go ahead for this requirement.
Regards
Mahendar.

hi,
If u want to allow user to create SO as much as available qty..? means system sud create SO for order qty is equal to availble qty ...? if yes
then go the availbality check and find out availability check and checking rule..
and again go to OVZ9 remove the check box check with out RLT from rep.lead time tab
Resul is: If u enter in SO a10 qty ,and if you have only 5 qty in hand or in plant ,then system after checking the items it will change the order qty in SO(i e 5) automatically,
Caprin

PO with Reference to RFQ (Qty, Price) could not be changed

Hi All
Please help how to restric user not to change Qty, Prices of PO if created with reference to RFQ.
Regards
Aamir

Hi Amir,
Goto SPRO->Mtrl Mgmt->purchasing->environment data->default attributes of system messages->system messages
Here for verison 00 application 06 msg quotation qty greater than po qty make it error message so that user cannot enter more than Quotation qty when he is making PO w.r.t to RFQ,
I'm not able to recall message number may be it is 078, just check there.
Regards

I need Checking in Production Order Qty

Hi all,
In our industry we are creating Production Order From Sales Order (MTO Scenario) by using T.Code CO08 or CO01 T.Code with out running MRP.Now if anybody intend to change the PO qty by using CO02 T.Code system allows and as a result the Sales Order Qty and Production Order qty mismatch.Now please give me solution so that anybody cannot change the production order qty and it must be same as sales order qty.
I am waiting for your valuable suggestion.
Thanks & Regards
Nirmal Sharma

Hi,
1. I dont think this is possible in any standard configuration.
2. You can utilise the exit EXIT_SAPLCOBT_001 and write our logic inside that
3. This exit is validated when ever we save the order,
4. The abap code should be written such that each time it should check for the sales order / itme no and check the quanity to be matching if it fails it should give error
note: in this case if you are trying to creat multiple production order for one single salesorder/item number then it will not be possible or another logic is to be incorporated.
reg
satheesh

RFQ table..

HI,
From which table do I get the following
RFQ QTy -
Field (ANMNG)
RFQ date -
Field (ANFDT)
I am unable to get it fron EKPO/EKKO.
Please help ASAP.
Regards,
Prasanna.

Dear Prasanna,
Please fulfill your requirement with below table.
Transaction: SE11,
Please ensure the tables EKKo is for all Purchasing Docuemnts Includes PO, Contract, and RFQ's.
Hence segregate your RFQ list by Docuemnt Type absed on your usage, Std RFQ doc type: AN.
RFQ Date:
              Table: EKKO
              FIELD: BEDAT
RFQ Qty:
              Table: EKPO
              FIELD: KTMNG
Hope this helps.
Note: For your information the fields you've mentioned is the fields in the structure, you cannot find teh same in the table. Hence you need to search the fields in the corresponding tables.
Njoy SAP
-Saravanaganesh

File is corrupted error while creating excel using xml

Hi have created one excel file using XML code and sent it to mail as attachement. But when i open it, it displays error message - file is corrupted and cannot be opened.
below is my code - please review and tell what is wrong in it ASAP :
* Creating a ixml Factory
   l_ixml = cl_ixml=>create( ).
* Creating the DOM Object Model
   l_document = l_ixml->create_document( ).
* Create Root Node 'Workbook'
   l_element_root = l_document->create_simple_element( name = 'Workbook' parent = l_document ).
   l_element_root->set_attribute( name = 'xmlns' value = 'urn:schemas-microsoft-com:office:spreadsheet' ).
   ns_attribute = l_document->create_namespace_decl( name = 'ss' prefix = 'xmlns' uri = 'urn:schemas-microsoft-com:office:spreadsheet' ).
   l_element_root->set_attribute_node( ns_attribute ).
   ns_attribute = l_document->create_namespace_decl( name = 'x' prefix = 'xmlns' uri = 'urn:schemas-microsoft-com:office:excel' ).
   l_element_root->set_attribute_node( ns_attribute ).
* Create node for document properties.
   r_element_properties = l_document->create_simple_element( name = 'TEST_REPORT' parent = l_element_root ).
   l_value = sy-uname.
   l_document->create_simple_element( name = 'Author' value = l_value parent = r_element_properties ).
* Styles
   r_styles = l_document->create_simple_element( name = 'Styles' parent = l_element_root ).
* Style for Header
   r_style = l_document->create_simple_element( name = 'Style'   parent = r_styles ).
   r_style->set_attribute_ns( name = 'ID' prefix = 'ss' value = 'Header' ).
   r_format = l_document->create_simple_element( name = 'Font' parent = r_style ).
   r_format->set_attribute_ns( name = 'Bold' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Interior' parent = r_style ).
   r_format->set_attribute_ns( name = 'Color'   prefix = 'ss' value = '#92D050' ).
   r_format->set_attribute_ns( name = 'Pattern' prefix = 'ss' value = 'Solid' ).
   r_format = l_document->create_simple_element( name = 'Alignment' parent = r_style ).
   r_format->set_attribute_ns( name = 'Vertical' prefix = 'ss' value = 'Center' ).
   r_format->set_attribute_ns( name = 'WrapText' prefix = 'ss' value = '1' ).
   r_border = l_document->create_simple_element( name = 'Borders' parent = r_style ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Bottom' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Left' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Top' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Right' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
* Style for Data
   r_style1 = l_document->create_simple_element( name = 'Style'   parent = r_styles ).
   r_style1->set_attribute_ns( name = 'ID' prefix = 'ss' value = 'Data' ).
   r_border = l_document->create_simple_element( name = 'Borders' parent = r_style1 ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Bottom' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Left' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Top' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Right' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
* Worksheet
   r_worksheet = l_document->create_simple_element( name = 'Worksheet' parent = l_element_root ).
   r_worksheet->set_attribute_ns( name = 'Name' prefix = 'ss' value = 'Sheet1' ).
* r_worksheet->set_attribute_ns( name = 'Protected' prefix = 'ss' value = '1' ).    " WORKING
* Table
   r_table = l_document->create_simple_element( name = 'Table' parent = r_worksheet ).
   r_table->set_attribute_ns( name = 'FullColumns' prefix = 'x' value = '1' ).
   r_table->set_attribute_ns( name = 'FullRows'     prefix = 'x' value = '1' ).
* Column Formatting
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '40' ).
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '90' ).
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '140' ).
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '150' ).
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '90' ).
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '90' ).
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '90' ).
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '90' ).
   r_column = l_document->create_simple_element( name = 'Column' parent = r_table ).
   r_column->set_attribute_ns( name = 'Width' prefix = 'ss' value = '90' ).
* Blank Row
   r_row = l_document->create_simple_element( name = 'Row' parent = r_table ).
* Column Headers Row
   r_row = l_document->create_simple_element( name = 'Row' parent = r_table ).
   r_row->set_attribute_ns( name = 'AutoFitHeight' prefix = 'ss' value = '1' ).
* RFQ No.
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'RFQ No.' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* RFQ Line Item No
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'RFQ Line Item No.' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* Material
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'Material' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* Quantity
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'Quantity' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* Order UNIT
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'Order Unit' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* Delivery Date
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'Delivery Date' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* RFQ Creation Date
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'RFQ Creation Date' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* RFQ Deadline Date
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'RFQ Deadline Date' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* Price
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
   r_data = l_document->create_simple_element( name = 'Data' value = 'Net Price' parent = r_cell ).
   r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
** Login
* r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
* r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Header' ).
* CONCATENATE 'Login - ' lv_date+6(2) '/' lv_date+4(2) '/' lv_date+0(4) INTO l_value.
* r_data = l_document->create_simple_element( name = 'Data' value = l_value parent = r_cell ).
* r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).
* Blank Row after Column Headers
   r_row = l_document->create_simple_element( name = 'Row' parent = r_table ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
   r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
   r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
* Data Table
   LOOP AT it_final1 INTO wa_final1.
     CLEAR l_value.
     r_row = l_document->create_simple_element( name = 'Row' parent = r_table ).
* RFQ No.
     r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
     r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
     CLEAR l_value.
     l_value = wa_final1-ebeln .
*    CONDENSE l_value NO-GAPS.
     r_data = l_document->create_simple_element( name = 'Data' value = l_value parent = r_cell ).           " Data
     r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).                               " Cell format
* Line Item No
     CLEAR l_value.
     r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
     r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
     l_value = wa_final1-ebelp.
     r_data = l_document->create_simple_element( name = 'Data' value = l_value   parent = r_cell ).           " Data
     r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'Number' ).                               " Cell format
* Material
     CLEAR l_value.
     r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
     r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
     l_value = wa_final1-txz01.
     r_data = l_document->create_simple_element( name = 'Data' value = l_value   parent = r_cell ).           " Data
     r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'String' ).                               " Cell format
* RFQ QTY
     CLEAR l_value.
     r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
     r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
     l_value = wa_final1-ktmng.
     r_data = l_document->create_simple_element( name = 'Data' value = l_value   parent = r_cell ).           " Data
     r_data->set_attribute_ns( name = 'Type' prefix = 'ss' value = 'Number' ).                               " Cell format
* UNIT
     CLEAR l_value.
     r_cell = l_document->create_simple_element( name = 'Cell' parent = r_row ).
     r_cell->set_attribute_ns( name = 'StyleID' prefix = 'ss' value = 'Data' ).
     l_value = wa_final1-meins.
     r_data = l_document->create_simple_element( name = 'Data' value = l_value   parent = r_cell

How to make a particular column non editable?
Make your style protected and pass that style name to your required column while passing data.
for example:
Find below the code for protection of a style.
Last two lines are very important.
* Style for Headert
   r_style = l_document->create_simple_element( name = 'Style'   parent = r_styles ).
   r_style->set_attribute_ns( name = 'ID' prefix = 'ss' value = 'Headert' ).
   r_format = l_document->create_simple_element( name = 'Font' parent = r_style ).
   r_format->set_attribute_ns( name = 'Bold' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Interior' parent = r_style ).
   r_format->set_attribute_ns( name = 'Color'   prefix = 'ss' value = '#B2FF64' ).
   r_format->set_attribute_ns( name = 'Pattern' prefix = 'ss' value = 'Solid' ).
   r_format = l_document->create_simple_element( name = 'Alignment' parent = r_style ).
   r_format->set_attribute_ns( name = 'Vertical' prefix = 'ss' value = 'Bottom' ).
   r_format->set_attribute_ns( name = 'WrapText' prefix = 'ss' value = '1' ).
   r_border = l_document->create_simple_element( name = 'Borders' parent = r_style ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Bottom' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Left' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Top' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Border'   parent = r_border ).
   r_format->set_attribute_ns( name = 'Position' prefix = 'ss' value = 'Right' ).
   r_format->set_attribute_ns( name = 'LineStyle' prefix = 'ss' value = 'Continuous' ).
   r_format->set_attribute_ns( name = 'Weight' prefix = 'ss' value = '1' ).
   r_format = l_document->create_simple_element( name = 'Protection' parent = r_style ).
   r_format->set_attribute_ns( name = 'Protected' prefix = 'ss' value = '1' ).

Subcontracting challan issue for end product with scrap.

Hi All,
I have one issue let me know how the system act in case of subcontracting challan process,
In our company we use one component and received two end product( one is final product and other one is scrap product)
My problem is how to treat this scrap in challan process.
Pl help me out.
Regards,
Zafina

Hi, Please use the exit to define how you want the system to consider Scrap in the subcontracting process.
Refer below exit for your problem,
1084323 USER-EXIT to update challan status if scrap is calculated
1103537 Correction to note 1084323 for ECC 6.0 Release
Please note the user exit will be accessed only if you were to write a code for it and you assigned/made 545 O as relevant to subcontracting
subcontracting scrap will work if the scrap percentage is defined for the component which is sent to the job worker. If you have a completely new material for scrap then this is not going to work as the system will never be able to assign the qty (mismatch of material code between the scrap material & the challan material).

Referance of subcontracting challan at time of GR

Hi Experts ,
i m not getting excise tab for refering subcontracting challan
Receiving material is semifinish material - all details r maintained in j1id
child material is raw material -all details maintained in jild
j1id details r -
plant -chap combination , cenvat determination , accessible value for both material
in cenvat dete input raw and output semifinish maintained
All Cin -subcontracting config is also done - subcontracting attributes in bussiness transactions and movement type groups r maintained
Now problem is that if i maintain Receiving material ( which is semifinish ) as RAw material in J1id(chapid-material combination ) then only i m getting excise tab in which there is refering subcontracting challan option available ..................but if i maintain Semifinish material as a RG1 in J1id then i dont get excise tab ............it is wrong ............how i can maintain semifinish material as a raw in J1id .it will create problem
so my requirement is although if i m maintaining semifinish material as a RG1 in J1id Which is i m going to receive from subcontractor , subcontracting tab should appear while making GR . Then only i will be able to reconsile the challan after making GR .
Please help me
Regards
Chandan

Please use the exit to define the way you want the system to consider Scrap in the subcontracting process.
1084323 USER-EXIT to update challan status if scrap is calculated
1103537 Correction to note 1084323 for ECC 600 Release
Please note the user exit will be accessed only if you were to write a code for it and you assigned/made 545 O as relevant to subcontracting
subcontracting scrap will work if the scrap percentage is defined for the component which is sent to the job worker. If you have a completely new material for scrap then this is not going to work as the system will never be able to assign the qty (mismatch of material code between the scrap material & the challan material).

System Message Settings

Dear Experts,
I've created the Purchase Requisition for 10 units... and PO created for all 10 units...
System not allow to change the PR now, for that we can set the system message :
Application area - 06
Message - 648.. either as warning or error..
In the same case.. PR created for 10, PO not created ,,, but RFQ created for 10 units... referring this PR..
Now i want to control the PR qty not to be reduced... less than the RFQ qty.. PLease let me know.. is this possible..
If so, pl let me know the message no.. where to set..
Thanks in advance

hi
Purchasing, the path to maintain warning & error messages is
Material Management->Purchasing->Environment Data->Define Attributes of System Messages

POs with   QUOTATION

Hi Experts,
I have to create PO wih QUOTATION
with ROUNDING value for the type of material is ( MPN Manufacturer part Number)
I am maintaining ROUNDING PROFILE in INFO RECORDS.
when i created PO with PURCHASE REQUEISITION it s triggering ROUNDING Profile QTY.
but when i am creating PO with   QUOTATION its not triggering ROUNDING PROFILE qty.
is there any configuration need for this scenario.. ??
HERS type material (MPN=Manufacturer Part Number )
Regards,
Anthyodaya.
Edited by: anthyodaya Reddy Nagaram on May 14, 2010 4:50 PM

Hi,
thank u for the reply,
quotation is not populated.   yes the system is taking from RFQ qty only...   how to do this scnario.. is there is any customizing required.. ?
Thanks in advance,
Anthyodaya.
Edited by: anthyodaya Reddy Nagaram on May 17, 2010 4:26 PM

Mismatch of qty in subcontracting challan reconcilliation

Hi,
When we issue the material using subsequent adjustment.During the reconciliation of subcontracting challan,
1) Challan quantity is not getting updated,
2) Material sent to item in subsequent adjustment is getting added in GR quantity, in subcontracting challan
E.g.
Subcontract PO qty: 10
Qty sent to vendor using subsequent adjustment: 5
After reconciliation of subcontracting challan,challan qty remains same i.e. 10.
GR qty in the challan is 5.
Please help.
Your quick response will be a great full.

It has been resolved at the author side.

Mismatch in Qty between MB51 and MCE3 / MCE7 / Table S012

Hi Experts,
At my client place i am running MB51 report for a material / vendor / particular period / plant / goods receipt movement type 101,102,105,106,122 so that i can get the total receipt quantity in that given period.
After getting the total qty of receipt from MB51, i am runnung 2 LIS reports -- MCE3(vendor analysis Purchase) and MCE7(material analysis Purchase).While comparing the GR qty from MB51 and LIs, getting some huge differences.The LIs report qty is mathcing with table S012.
What could be the issue for differences in qty between MB51 and MCE3 / MCE7.How to analyse the issue and how to go about to overcome the differences.
Thanks.

Hi,
did you see any update problem in your system or any unexpected system restart ? If you say yes, your LIS tables could give different results when we compare with the MB51.
The solution,
Before you get there, first thing to do you need to find which plant, which materials, when and what time it happened. If you could find those information it would help you to fix the problem easly.
For example between 01.01.2009-31.01.2009 and in the plant ZZZ there is a difference amount of quantity in mb51 and MCE3.
And than, using OLIF transaction you need to create a snapshot in a "&(1" version (this is a temporary data), for ZZZ plant between 01.01.2009-31.01.2009. It could take time to create dont worry when you run the program.
When you create the data from OLIF, now using mce3 or mce7 or both you could compare those reports with mb51. But one thing that you need to be careful about that is while using mce3 or 7 you need to choose version "&(1" which we created from OLIF.
If It's OK,
it's time to go to LIS copy management.( using spro -> Logistics - general -> LIS ->Logistics data warehouse -> Data basis -> Tools -> Copy management or transaction MCSZ)
Be careful about before copy process you need to delete 000 version(production version) for specific date time and plant !!! And now you could copy.
PS: Both delete and copy operations could be done by MCSZ.
If It's NOT OK,
you need to check your parameters while using OLIF. And last thing, Each time before you using OLIF you should delete that temporary version from MCSZ.
Best regards
Çağatay ÖZAK

PO qty reduced who brings the cart into cockpit

Hi all
scenario
sc created with 2 qty
PO created by Buyer 2 qty via cockpit .
Again Buyer received a call from requestor that requestor needs only 1 qty rather than 2.
then again BUYER changed the qty to 1 from 2 via me23n. Now again shopping cart venture into cockpit due to mismatch between sc qty and PO qty .
no good receipt done so far since so far buyer did not send the PO to vendor.
how sc comes to cockpit after some time? who is really doing this wotk get status - variant which data plays important role here. or clean job brings... confusion.
can you clarify this trivial things to me..
sc folow on docuemnts updates with PO qty as 1 . but still sc did not come to cockpit.
i am sure it will come shortly i.e sc comes to cockpit. i wanted to who does this job?
if possible answer this.
item guid and header guid sc where it stored in ECC table. i am pretty sure , they were stored in some tables.
br
Muthu

PR -2 qty --> soco -> sc 2 qty --> PO 2 Qty -->changed to PO 1 QTY
status run and clean run well.
still i am looking for this sc 1 qty in the cockpit. Waitinting and waiting...
Muthu
works
sc 2 qty -PO 2 Qty -
po 1 qty -
sc comes to cockpit.
SG:- Stop the get status job . reduce the PO qty 1 from 2 qty thought the sc comes to cockpit. inscrutable.
thanks
Finally, I tried putting 0 in last.. days and running BBP_GET_STATUS_2 in debug mode. From what I see it is looking at all the SC's in the system and trying to update status for each of them. We normally run this job with 30 days on a hourly basis.
Yes. during that time all locks will happen .did you notice in sm12 . no one can perform any activity.
i am looking for dalily updates happened in ECC and it must be updated in SRM - with which variant.
since i ahve some special request .
kindly advise.
How long it took in production . hope it may take lot of time. i am interested to know when do you run this job ? at night no business hours ..since our volume of carts are more...it runs more than 3000 secs in testing envt it self.
Muhtu

GR and IR mismatch report

Hello Team,
Please let us know any standard report for we can run to view GRIR mismatch but the IR and GR quantity is already equal and the IR and GR price has mismatch.
Regards
SANGEETHA

Hi,
it is not solution, what i am sating GR QTY 10 amount value 1000 rs and IR Qty 10 but amount value is 950. Theeir is differenece between GR amount value and IR amount value.
Is their any standard report to check list of po's difference between GR and IR quanity match and amount value is not match.
Regards
Sangeetha

Data Migration from 11i to R12 Global - Open POs,lines, receipts & on hand upload, Is it possible to do the onhand qty upload with over riding of all receipts which uploaded against Open PO lines?

Hi Friends,
We are in a phase of data migration from 11i to R12
I was discussed with client & they wants extraction of all open POs which was generated after 01 Jan 2014 to till date in 11i.
Condition for open POs is PO qty-received qty=>0
critical Example for open PO is :PO no: 10 has 4 lines, 3lines full qty has been received & for 1 line partial qty(say 50 out of 100) received.
in this case he wants in R12 uploading as PO no:10 should entered as open PO with all 4lines & 3 lines complete receipt should be done, for 4th line partial qty i.e 50 should be received.
the question is if we upload on hand qty first, then open POs & receipts, it will increase the onhand qty in new system(mismatch of on hand qty's 11i to R12)
Is it possible to do the onhand qty upload with over riding of all receipts which uploaded against Open PO lines.
Or Please advice best solution.
Thanks & Regards
Giri

adetoye50 wrote:
Dear Contacts Journal Support Team,
FYI, this is a user to user support forum. You are NOT addressing Apple here.
Honestly, I doubt anyone is really going to take the time to read the novel you have written.

PR & RFQ QTY MISMATCH

Similar Messages

Maybe you are looking for