Quality info records: how to handle same supplier with different sourcing

hi all
I have material which comes from same supplier but different sourcings: as in I have one vendor supplying it but it can come from different sites; as some sites might be approved and others not, how can I differentiate that?
thanks
Alisa

You need to use the MPN profile functionality that is a standard part of SAP.
In Config under the purchasing define the MPN profile. There are several options you can turn on/off including info records.
You assign the MPN profile to your material. It now is considered by SAP to be an internal material number.
You then create a HERS material type for each separate manufacturer material number you have. You only need the purchasing view for these materials. You can also create purchasing text views, classification and some others if you wish.
In the SAP approved vendors list (AVL), you then assign each manufacturer vendor(s) with the HERS material created.
You create a Q-info record for each manufacturer/HERS material combination.
Now, when you specify the internal material number in a PO, the system will tell you to order the MPN material. When you do the drop down for the material now, it will show you the approved manufacturers allowed in the AVL for the ordering plant.
When the 01 inspection lot is created you will have a vendor number as well as a manufacturer's number in the inspection lot. The DMR can be done by the manufacturer or the vendor depending on how you set up the inspection plan. Q-info record will be used accordingly.
Take a look at it and research it. It's not hard to set up.
FF

Similar Messages

How to handle same product with different part numbers and pricing in SAP.

I am a new user and want to learn if the following scenario can be handled by SAP.
Our business buys a product from a supplier which has 2 different part numbers and prices. It is the same product. One is the primary product whilst the other is available only as an upgrade option with a different part number to a mainline product at a cheaper price .
Our issue is that we sometimes buy the upgrade option with a mainline product to get the better price even though these go into stock. Basically we need to have the items linked with both part numbers in SAP at different prices but inventory both in and out only going against the primary part number. Any ideas?

Thanks Jitin
I did give them different part numbers and then attached a Bom containing the primary part number against the upgrade option however I really need to have the secondary item as a sales and purchase item but non inventory so the stock comes from the primary part. Ideally if we receipt the goods in as the secondary number the inventory goes to the primary part. If the second number is an inventory item then I have the issue of the same part with different part numbers sitting in stock at different prices and having to rely on employees understanding the difference.
Sorry to be so confusing. I will do some more testing over the weekend and see if I can find a suitable solution.
Thanks
Martin

How to handle Fact tables with different granularity in OBIEE 11g RPD

Hello Everyone,
I have got stuck here and need your help.
I have two fact tables (Say F1 and F2... F1 is containing data at month-level and F2 is containing data at day level) and one Date DIMENSION TABLE. Date_Code is the PK of Date dimension table.I need to use time-series functions also.
Can anyone tell me how to model this requirement in the RPD.
Can we use a single dimension table(Here Date dimension table) with two fact table of different grainularity? What would be the best way to implement this requirement?
Thanks in advance :)

Hi Veeravalli,
Thanks for your reply :)
Let me explain the problem in more detail. I have one Date dimension(Date_Code,Month_Code,Quarter_Code,Half_Year_Code,Year_Code). Here Date_Code is the PK.
In F1---->Date (Using Month_Code key)
F2-------->Date (Using Date_Code Key)
Level based hierarchy is there starting from Year to Date.Each level has PK defined and chronological key selected.
F1 has level set to Month and F2 has level set to Day.
Now if i am using ago() function on measure of F2 (having day level data) then it's working fine but if i am using ago() function on measure of F1...I am getting an error at Presentation service: Date_code must be projected for time-series functions.
So the whole issue is with time-series functions. As per my research...I think for time series the tables in the physical model containing the time dimension cannot join to other data sources, except at the most detailed level but here i am joining with F1(using Month_Code which is not the most detailed level).
So kindly let me know how to achieve this in rpd?

How to exclude same field with different combinations in selction

hi friends,
   i have small requirement please suggestion me..
i have 2 r multiple combinations
BLART(Doc Type) - DX, CM
BLART = RV and ZTERM = z041
BLART = RC and ZTERM = N005
If My requirement exclude in Select statement i will do, BUt My requirement Before select statement i want to maintain the Exclue data after used in to select statement. How it do that ?
Why this requirement is Given Means If i want to exclude some more combinations data add the Before select statement.
so please any body know please suggestion me.
thanks in advance

Maybe try something like this i.e. with brackets() as below. I use 1 combination for example:
RANGES: rv_doc FOR bkpf-blart.
   rv_doc-sign = 'E'.
   rv_doc-option = 'EQ'.
   rv_doc-low = 'RV'.
   APPEND rv_doc.
RANGES: rv_zterm FOR bkpf-zterm.
   rv_zterm-sign = 'E'.
   rv_zterm-option = 'EQ'.
   rv_zterm-low = 'N005'.
   APPEND rv_zterm.
SELECT bukrs
            kunnr
            belnr
            etc...
       FROM bsid
       INTO TABLE it_bsiad1
      WHERE kunnr IN s_kunnr
      AND umskz <> 'D'
     AND budat LE ty_date
     AND blart IN excl_doc
     AND (blart IN rv_doc AND zterm IN rv_ZTERM)

Quality info records: different pack configurations for same raw material

how can i differentiate different pack configuration for same raw material in quality info records, as one might approved and the other not? that is, besides creating different material master for each packaging?
thanks
Alisa

You need to use the MPN profile functionality that is a standard part of SAP.
In Config under the purchasing define the MPN profile. There are several options you can turn on/off including info records.
You assign the MPN profile to your material. It now is considered by SAP to be an internal material number.
You then create a HERS material type for each separate manufacturer material number you have. You only need the purchasing view for these materials. You can also create purchasing text views, classification and some others if you wish.
In the SAP approved vendors list (AVL), you then assign each manufacturer vendor(s) with the HERS material created.
You create a Q-info record for each manufacturer/HERS material combination.
Now, when you specify the internal material number in a PO, the system will tell you to order the MPN material. When you do the drop down for the material now, it will show you the approved manufacturers allowed in the AVL for the ordering plant.
When the 01 inspection lot is created you will have a vendor number as well as a manufacturer's number in the inspection lot. The DMR can be done by the manufacturer or the vendor depending on how you set up the inspection plan. Q-info record will be used accordingly.
Take a look at it and research it. It's not hard to set up.
FF

Avoid Purchase Order without Quality info Record

Hi All,
I am facing the problem, i.e i want to avoid creating purchase order if the quality info record is not maintained.
Can we do it ?????, If yes please suggest me how to go about it & what are the control points for the same.
Please reply ASAP.
Arun

Hi
In material master If u activate QM proc key.And enter a valid Control key like 0001.system will not allow u to create PO without Info record(QI01).
If any queries let me know.
Gopi

BAPI for Sampling scheme and Quality Info Record in QM Module.

Hi techies,
I have a two object(Sampling Scheme,Quality info record) for which i need a BAPI for uploading the data.
Please tell me if any one knows.
Richard.

Vineeth,
Usually, I wouldn't think the follow-up action would be an issue with system performance. You say 7000 items, but do you mean 7000 UD's? I.e. an inspection lot of 1000 units isn't unusual and that would be 7 inspection lots. You've also now said that the program needs to look across plants for UD rejections and for notifications. That is another level of complexity.
While the UD follow-up action should still be able to handle that, I can't say it won't affect performance. I was going to suggest you have it only run on certain UD codes, but since you now need to reveiw this across plants that might not work.
What happens if my vendor/material is in a skip stage at plant A and Plant B opens a notification agains the vendor? Since there is no UD, the follow-up action wouldn't run and change the DMR at plant A.
If you need to look at a bunch of stuff, instead of the follow-up action, you may need to run a program in batch and have it run once an hour or every 10 minutes. Depending on how you write it, it could be pretty efficient.
Craig

Transferring Quality Info record longtext to PO

Hi ,
We have PRs created from Maintenance Order, from PR we create PO , for the materials we have QM activated & Quality Info record longtex is maintained in QI02 , we would like this to be displayed under PO Texts tab , ..pls let me what setting needs to be done ..
regrds
pm

Hi ,
U cannot copy the long text from the Quality Info Record to PO text in PR. Because there are only 4 source objects from which we can fetch the text & these are material master record, network, RFQ, purchase order.
You need to do some enhancement for the same.
Regards,
Satpal

Status profile - Quality Info record

Hi,
Pls explain about status profile: QM_P_DOL -
Status check DOL.
Waht is DOL?
Why is required?
Reg,
RPV.

Hi,
Status profile is created by the user in general status management and used to control user statuses
In a status profile you can:
Define the sequence in which user statuses can be activated
Define initial statuses
Allow or prohibit certain business transactions
Status Profile Assigned to Quality Info Record:
Use : The supply relationship can run through a sequence of statuses that you define in a status profile. The sequence of statuses for the supply relationship is updated whenever inspection lots are accepted in the usage decision.
If you assign a status profile that has a mandatory sequence of statuses to a vendor relationship, the system creates inspection lots for origin 01 with an inspection type appropriate to the status of the vendor relationship.
supply relationship : A business link with vendor or customer.
Quality Management information for these business links are managed in the SAP system using the following master data:Vendor master record and Info record with reference to vendor, material and plant.
SAP standard User profiles starts with QM_P for supply relationship. In your case
QM_P stands for supply relationship and DOL might be User notation.
Hope it is clear to you.
Regards
Venkat.V

Quality info Record for SD

Hi all
Let me know about Quality info Record for SD (QV51, QV52, QV53). I want to know whether Info record is created or not for particular customer.
I have to create a alert to QM Department. Whenever usering create a sale order, system should check info. record is available or not for the Customer for sale order. If info. record is not there, we should trigger alert to QM department for creating alert.
How can i proceed?

Hi Muthu,
The info record has to data sections (look in Goto menu in the Info Record screen):
i. General Data (NOT at POrg and Plant level)
ii. POrg. Data 1 (POrg. and Plant level)
iii. POrg. Data 2 (POrg. and Plant level)
iv. Text (POrg. and Plant level)
Purchasing info records determine the prices suggested in purchasing documents in two ways:
The system,
1st searches under POrg. Data 1 - Conditions:
Conditions are included if they have been maintained for an info record manually or from a quotation (but can be changed manually afterwards)
2nd searches under POrg. Data 2 Last Purch Doc.:
If an info record does not contain any conditions (under POrg. Data 1), the system reads the number of the last purchasing document in the info record and then suggests the price from this document.
Info Update indicator for Conditions (in PO, RFQ/Quotation, Contract) :
for PO the update occurs in POrg Data 2 (last purch doc)
for RFQ/Quotation - the update occurs at POrg Data 1 Conditions (can be changed manually afterwards) and POrg Data 2.
for Contract the update occurs at POrg Data 1 - Conditions, IF at the time of the contract creation there is No info rec. Otherwise the info rec is updated with the last release order under POrg. Data 2.
cheers,
Hema.

Reg Quality Info Record

Dear ALL,
please give me a advice let us say we have a vendor ven0001 who is manufacturing a material a001 in 3 of his plants( plant-0010, lant 0020 and plant 0030 and these three are manufacturing plants of vendor) can we put a control in our plant 0001 that when we make a quality info record for material a001 in plant 0001 with vendor ven001 can we specify that he supply from plant 0010 only
please advice
Thanks in advance
Regards
venkat

Yes. You can meet this requirement using MPN materials.
First you create three mfg numbers, one for each of the manufacturer's plants. You link these as partners to the main vendor number if you want.
You specify in your material A001 an MPN material profile. This profile is set up in configuration and one of the items is Q-info records.
You now create three material masters, (material type HERS). This only needs a purchasing view. In here you specify the internal material number, (A001) as well as the manfacturer number. You can also specify a manufacturer's part number if you want to in here.
You can now create a Q-info record for each of three HERS materials. You block two and approve one. Now you can only order from the one approved site.
You can also usee the AMPL table, (transaction MP01/MP02) if you want to track and set up more specific info. This is configured in the MPN material profile that was mentioned above. In here you can specify valid from and valid to dates and set these records up plant by plant and have additional block functions in here.
FF

BAPI or IDOCs for Quality info records

I want to know which BAPI or IDOCs is used to upload the Quality info records data from legacy system to SAP.

Hi Raghu
Below is the BDC program I was used for the same.
Program Name : YX30_UPLOAD_QUALITY_INFO
Author : Rameshwar Yadav *
Date : 2006-11-27 *
Description : The purpose of this program is to upload the *
Quality Info Record for I30 System *
Original Transport Number : I30K903055 *
SYS id: SYS_30_1502_03_41_Upload Quality Info Records *
TDS id: TD_30_1502_03_41_Upload Quality Info Records *
UT ID: UT_30_1502_03_41_Upload Quality Info Records *
======================================================================
Change History *
Date | Change No | Name | Description *
yyyy/mm/dd | AAAYYYYMMDD | xxxxxxxxxxxx | *
REPORT YX30_UPLOAD_QUALITY_INFO MESSAGE-ID yx30_conversions
no standard page heading line-size 255.
include yx30_upload_quality_info_top. "Include for Variable Declaration & Selection Screen
include yx30_upload_quality_info_data. "Include for File read & Authority Check
*& At Selection Screen Output *
AT SELECTION-SCREEN OUTPUT. "PBO
PERFORM fill_parameters.
*& Start Of Selection Event *
start-of-selection.
Perform Authority_check. "Subroutine for authority check
Perform prepare_file. "Subroutine for preparing file
perform file_read. "Subroutine for File read
perform update_qi01. "Subroutine for Uploading data
perform write_error_log1. "Subroutine for writing error log
*& Form write_error_log
text
--> p1 text
<-- p2 text
*& Include YX30_UPLOAD_QUALITY_INFO_TOP
Type Declaration
Types: Begin of type_qtyinf,
matnr type matnr, "Material No
lieferant type char10, "Vendor
werk type werks_d, "Plant
frei_dat type char10, "Frei_Dat
stsma type char8, "Stsma
anwso_01 type char1, "ANWSO(01)
anwso_02 type char1, "ANWSO(02)
anwso_03 type char1, "ANWSO(03)
end of type_qtyinf.
Internal Table Declaration
Data: itab_qtyinf type standard table of type_qtyinf. "Internal table for QTYINF.
Work Area Declaration
Data: wa_qtyinf type type_qtyinf. "Work Area for QTYINF.
Variable Declaration
Data: v_file_qtyinf type string, "Source File Name
v1 type string,
v2 type string,
v3 type string,
v_file_return type string,
v_lin TYPE n.
*Selection Screen Declaration
selection-screen *
SELECTION-SCREEN BEGIN OF BLOCK blk1
WITH FRAME TITLE text-s01.
PARAMETER:
p_sysid(3) TYPE c OBLIGATORY , "Source System
p_bukrs(4) TYPE c OBLIGATORY , "Source CompCode
p_samshr type char30 lower case obligatory default '/sap_upload/' , "Samba Share Drive
p_object TYPE CHAR10 OBLIGATORY default 'MAT' . "Migration Data Object
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN SKIP 3.
PARAMETER:
cb_pfill TYPE c AS CHECKBOX DEFAULT 'X' . "Prefill values?
SELECTION-SCREEN COMMENT /1(79) text-s1a.
SELECTION-SCREEN BEGIN OF BLOCK blk3
WITH FRAME TITLE text-s03.
PARAMETER:
pa_filn1(500) TYPE c LOWER CASE
VISIBLE LENGTH 50 , "Filename AppServer
pa_dlimt TYPE c DEFAULT ';' . "Field Delimter
SELECTION-SCREEN END OF BLOCK blk3.
include bdcrecx1. "Include for the subroutine
*& Include YX30_UPLOAD_QUALITY_INFO_DATA
*& Form file_read
Subroutine for reading the source file into internal table
--> p1 text
<-- p2 text
FORM file_read .
DATA:
single_line TYPE string .
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_qtyinf FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
DO.
READ DATASET v_file_qtyinf INTO single_line. "Reading the content of file into line
IF sy-subrc = 0.
IF sy-index > 1. "skip header-line
SPLIT "Split the content of line into work area
single_line
AT ';'
INTO
wa_qtyinf-matnr "Material No
wa_qtyinf-lieferant "Vendor
wa_qtyinf-werk "Plant
wa_qtyinf-frei_dat "Frei Date
wa_qtyinf-stsma "STSMA
wa_qtyinf-anwso_01 "ANWSO_01
wa_qtyinf-anwso_02 "ANWSO_02
wa_qtyinf-anwso_03. "ANWSO_03
APPEND wa_qtyinf TO itab_qtyinf. "Appending Work Area to internal table
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE DATASET v_file_qtyinf. "Closing the files
ELSE.
MESSAGE e015 .
ENDIF.
DESCRIBE TABLE itab_qtyinf LINES v_lin.
IF v_lin LT 0.
MESSAGE e016 .
ENDIF.
ENDFORM. " file_read
*& Form fill_parameters
Subroutine for getting the file name
FORM fill_parameters .
IF cb_pfill = 'X'.
Preparing QTYINF File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO pa_filn1.
ENDIF.
ENDFORM. " fill_parameters
*& Form Authority_check
Authority Check
--> p1 text
<-- p2 text
FORM authority_check .
Authority Check For the Migration
AUTHORITY-CHECK OBJECT 'YX30_MIGR'
ID 'SYSTEM' FIELD p_sysid
ID 'BUKRS' FIELD p_bukrs
ID 'YX30_DMOBJ' FIELD p_object
ID 'ACTVT' FIELD '16'.
IF sy-subrc <> 0.
MESSAGE e010 WITH p_sysid p_bukrs p_object.
ENDIF.
ENDFORM. " Authority_check
*& Form prepare_file
text
--> p1 text
<-- p2 text
FORM prepare_file .
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO v_file_qtyinf.
CLEAR v3.
CLEAR v2.
Prepare Return File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_RETRUN_LOG_' p_bukrs '.CSV' INTO v2.
CONCATENATE '/sap_upload/' v3 '/' 'MAT' '/' v2 INTO v_file_return.
ENDFORM. " prepare_file
*& Form update_qi01
text
FORM update_qi01.
PERFORM open_group. "Opening a session
CLEAR wa_qtyinf.
LOOP AT itab_qtyinf INTO wa_qtyinf.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0100'. "Subroutine for mapping data
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-MATNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'QINF-MATNR'
wa_qtyinf-matnr. "Mapping the material
PERFORM bdc_field USING 'QINF-LIEFERANT'
wa_qtyinf-lieferant. "Mapping the vendor
PERFORM bdc_field USING 'QINF-WERK'
wa_qtyinf-werk. "Mapping the plant
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=STAN'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-STSMA'.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma. "Mapping the status
PERFORM bdc_dynpro USING 'SAPLBSVA' '0201'.
PERFORM bdc_field USING 'BDC_CURSOR'
'J_STMAINT-ANWSO(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OKAY'.
IF wa_qtyinf-anwso_01 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01. "Mapping the anwso(01)
ELSEIF wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02. "Mapping the anwso(02)
ELSEIF wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03. "Mapping the anwso(03)
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ENDIF.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-FREI_DAT'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=QMBU'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma.
PERFORM bdc_transaction USING 'QI01'.
ENDLOOP.
PERFORM close_group. "Closing the session
ENDFORM. "update_qi01
*& Form write_error_log
text
--> p1 text
<-- p2 text
FORM write_error_log1 .
DATA:
single_line TYPE string,
v_msg TYPE string,
v_msg1 TYPE string.
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_return FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
CONCATENATE text-020 v_lin INTO v_msg SEPARATED BY space.
CONCATENATE text-021 v_lin INTO v_msg1 SEPARATED BY space.
TRANSFER: v_msg TO v_file_return.
TRANSFER: v_msg1 TO v_file_return.
WRITE:/ v_msg.
WRITE:/ v_msg1.
ENDIF.
ENDFORM. " write_error_log
Regards,
Sree

Status profile in Quality Info Record

Hi,
How do I default a status profile in the Quality Info record. Can this be achieved through customization. Any pointers would be greatly appreciated.
Regards
Kiki

Hy Kiki,
Use Transection Code OQBA and create your screen varients with required User status.
It will works only with Transection Code QI06 (Mass processing Q info Record)
Regards
Dhaval

Sample managment and quality info record

Experts
I have a scenario like below
If my physical sample was approved (inspection type 15) by a usage decision
i need system should create a automatic quality info record for this material and vendor combination
How can be possible
pls give me some details step
Faisal

In the selected set of Usage decision there is provision of followup action.
In followup action customization you can create you own function module.
In this customized function module you can call program RQBAAM10 in the background to create quality infor record.
But here you have to make sure that you should have "control key " in place for that material -plant combination.
you can also explore Function module QINF_WRITE_DOCUMENT

Need BAPI for change of quality info record (Tcode: QI02)

Hi,
Currenrly iam using BDC for creation of Quality info record (QI01) and now i need to do this creation as a back ground task. for which BDC is not supporting. So, i need to know the relavent BAPI for creation/change of QI02.
Regards,
Krishna.

Hi,
Have you tried doing this in ECATT??
See this Link:
http://help.sap.com/bestpractices/BBLibrary/Documentation/G09_BB_InstallGuide_EN_DE.doc

Quality info records: how to handle same supplier with different sourcing

Similar Messages

Maybe you are looking for