Vendor creation process

Hi,
I am trying to design a process for vendor master creation and need some guidance. There is QM involved in the process as well and QM has to finally bless the vendor and allow supply chain to buy from him.
The process I am thinking of is as follows
A new vendor request is submitted offline to the master data group
Some one in the group creates the vendor via MK01.
At this stage I want the vendor to be created with an automatic block (can I run MK05 in the background to block it the moment it is created?)
Then the master data group creates the purchase info record and the quality info record (here the system allows me to create the QIR without the QM procurement key turned on. I want a hard stop. In other words the material should be assigned first
the inspection type 01 and the QM control key)
The finance goes and extends the finance views to the vendor master.
Then the master data group goes ahead and takes the block off from the vendor master.
Is this a process which is usually followed at most companies and does it sound feasible ? I want to make sure that suppply chain can still order from the vendor (at risk) even if the vendor is not completely qualified by the QM group for that material.
Thanks

Dear GS,
As per my experince with different clients - The pracitce you are going to opt or thinking to implement is not followed in MOST of the comapnies. I do agree that QM should bless the vendor but why QM wants to come in picture before procuring a material. If your QM team really wants a role then they can visit the Vendor's premise to check his capabilities.
Once you purchase material from Vendor then based on QM you can return or keep the material. In Purchase order you can specify your requirement about that good.
Same point I am not denying that this requirement may not fullfill but it is not worth to put efforts in this process.
Thanks

Similar Messages

Vendor creation default values

Where is the config for setting up default values on vendor creation process- fields like- "check double invoice" ?
Thanks
Raj

Hi Rajendra ,
Screen control for the vendor is controlled by the Account group you assign to them. So go to IMG> Financial accounting > Account rec. and payables> Master data > Define account group with screen layout. Here you can find and change the the fields status for General , company code and purchasing data.
Hope it helps.
Thanks
Kiran
P.S Pls award points if you find the answer is helpful.

Workflow for Vendor Creation through a portal.

Hi All Workflow Experts,
I have a scenario here.In my project vendor is created through a portal.On submit button from portal the workflow is to be triggered.I have to design the workflow process.So can you please guide me through what all should i consider while i design this workflow?
This is my first workflow assignment so if you explain in detail it will be a great help.
I will just pen down what all scenarios i can think of:
1.Start workflow after vendor creation or modification.
2.Check whether approver are maintained in Org structure through standard FMu2019s.
3.Check If approvers are maintained ?
4.If yes,approve or reject the vendor.
5.If no,get the agents from the custom table who can take an action on this.
This is what i can think of.
Please guide me.
Thanks in Advance,
Saket.

The corresponding BO related with the vendor creation or changing is LFA1 but this Business object doeanot have any events that are related to Create and Change , so try to create a ZLFA1 and add you own events or make use of delegation concept where you will create a delegation for LFA1.
For your first isssue
Start workflow after vendor creation or modification
EXIT_SAPMF02K_001 Vendors: User Exit for Checks prior to Saving is the user exit where in you can call the workflow when ever you change or create , because this user exit will trigger when ever you try to save the vendor. so i think you can make use of this user exit
For your second Issue
Check whether approver are maintained in Org structure through standard FMu2019s.
Make use of SWI_GET_USERS_OF_ORG_UNIT this fucntion mdoule to get the user of the ORG unit
or you can create a Rule(for determining the agents dynamically) to find the approvers.

Vendor Creation ,Partner role OA not allowed for Vendor of a/c group ZLOV

Dear Freinds,
I am facing problem of Vendor creation , i am getting message PARTNER ROLE OA NOT ALLOWED FOR VENDOR OF ACCOUNT GROUP ZLOV.
While creation of Vendor in Partner function i could not enter partner number, system is not accepting any data, message is getting as above.due to which i could not create any vendor.
Presently I am in process/ setting of ERS functionality in MM,
now all my Vendor creation is stuck up ,
please help me how to solve the problem
Regards
Dilip

Hi Dilip,
Check first have you Define Permissible Partner Roles per Account Group..
Check the path:
SPRO-Materials Management-Purchasing-Partner Determination-Define Permissible Partner Roles per Account Group
Here check whether OA is assigned with ZLOV or not...If no then click on new entries and enter partner function as OA and Vendor account group ZLOV...Save nd come out...
Now proceed...Hope it helps..
Utsav

Vendor create process using workflow

hello,
I have been assigned a project to desgin a process to automatically create a vendor. below is what I think has to be done. can this be reviewed to see if this is the correct approch and if not, suggest a better approach.
1) the vendor will sign onto our portal and submit their information to have them created as a vendor in our system. this information will be stored in a custom table
2) the portal process will have a ABAP program that generates the screen for the user to enter thier data. this program will also start a workflow that will send a notification to a person inside our company for them to review the information and decide weather the vendor can be added.
3) if the person approves the request, the workflow will submit a process to create the vendor, and send a approval email to the vendor
4) If the person rejects the process, the workflow will send an rejecction email will be sent to the vendor
I am in charge of creating the workflow and submitting the vendor create process
thanks in advance for the help

Hi Anil
Take a look at the Workflow collateral located on http://otn.oracle.com/products/integration/content.html.
I'd also suggest looking at the Sample Workflow Processes included with Oracle Workflow.
There are also some on demand Oracle iLearning courses (ilearning.oracle.com) which should be very useful for you.
Cheers
Mark
Hi,
Could anyone give me a case study describing how to create a new process using workflow builder? Where are the notifications saved in the database? Where is the process saved? Give me a general flow of events in the creation of, say a document management process wherein all these details are specified. A document containing the whole flow involved in the creation of a process using workflow builder. What all PL/SQL procedures I need to write and all. I have both workflow server and builder installed.
This would be of immense help.
Regards
Anil

Vendor Creation Via OAWD using workflow

Hi,
We are currently using SAP Archvelink for attaching vendor invoices to FI docuemnt via FB60 and MIRO using a basic workflow function
We want to be able to use the same process ie OAWD to be able to initiate the process of creating a vendor via XK01. The user woudl receive an authorised vendor creation PDF form that they woudl then attach to the vendor when cretaing
I have tried to configure a new document type and have assigned to object type LFA1 in transaction SOA0. However, when I try to maintain the workflow parameters to link to transaction code XK01 in transaction OACA I get the following message
Parameter TRANSACTIONCODE does not exist for method CREATE of object type LFA1
I dont know what to do (or if it is possible) to enable the "CREATE" method for object type LFA1
Thanks in advance

I solved my own problem.
I had to configure OAWS first then it allowed me to add create in SOA0
Edited by: Tracee on Sep 14, 2010 7:43 AM

Vendor creation types

hi guys can anyone tell me how many types of vendor creation?and tcodes

Hi,
The types of vendor depends on customer business process and involved process. You can vendor types as Domestic Vendor,Import Vendor,Capex Vendor,Employees Vendor & One Time Vendor. Each type must have different vendor account group so as to also definitely different number ranges.
You can create vendor in t.code: XK01 ( centrally). Also vendor can be created in t.codes: MK01(purchasing) & FK01( finance)
For more check link for XK01:
http://baylor-help.bcm.tmc.edu/content/create_vendor_master_-_xk01/qr_step/html/index.htm
Regards,
Biju K

From Vendor Creation to Payment of Supplier (New User Here)

Hi,
Can anyone here could help me find a link or any softcopy of document that will help me learn more about the process of vendor creation up to the payment of supplier process. Right now I'm using an Oracle Dev module so we can tests for ourselves how the system works. The problem is that we are all Newbie.
Hoping that someone can help me here.
Thanks,
Ace

echo "alias ls='ls --color=auto'" >> ~/.bashrc
That will append the alias mentioned in post 2 to your .bashrc which is where aliases are stored (you should run this as user for user's bashrc and root for root's bashrc). You will need to logout or issue
source ~/.bashrc
to get it to work.
For example I've aliased ls to ls -sh to give me file sizes
edit: fixed typo
Last edited by SS4 (2011-01-17 21:39:35)

Error in Vendor Creation

Hi,
In Vendor creation , while selecting the Country as United States ( US) in Vendor address the following error message is displayed
"Communication error with the external tax system (VERTEX_MS0018)
Message no. TAX_TXJCD864 "
How to solve this issue?????
Regards,

Hi,
Check the following entries.
OBCO : Check the schema TAXUSX (VERTEX Standard Jurisdiction Code)
OBCP : Select the costing sheet TAXUSX, check the tax jurisdiction codes
IMG>Financial accounting new > Financial accounting Global settings > Tax on sales/puchases >basic settings > External tax calculation.
Take FI consultant help make necessary settings.
Regards,
Chandra

Getting syntax error in "SAPLBBP_PDH_CUF" in shopping cart/RFx/PO creation process in SRM7.0.Is it Patch issue?

Getting syntax error in "SAPLBBP_PDH_CUF" in shopping cart/RFx/PO creation process in SRM7.0.Is it Patch issue?

Hi, something wrong with your customer fields...
Please, check them...

PO Creation Process in Classic Scenario

Hi
I want to understand the exact PO creation process in a classic scenario. Once the buyer clicks on 'Create Purchase Order' in the SOCO, what are the series of steps that are triggered till the PO number gets displayed in the SOCO screen?
I assume that the shopping cart has all required data and ready for PO creation.
With Regards
Sathya

Hi,
The shopping cart is created and approved in SAP Enterprise Buyer. The remainder of the procurement process takes place in the backend ERP system(s) and all other follow-on documents, such the purchase order, goods receipt/service entry sheet and invoice, are located there. With SAP Supplier Self-Services, you have partial supplier involvement for the operational procurement business scenarios when buying materials. There is no support for services.
Shopping Cart
SAP Enterprise Buyer
Approval
SAP Enterprise Buyer
Purchase Order
Backend system
Goods Receipt
Backend system (can be pre-entered in SAP Enterprise Buyer)
Invoice
Backend system (can be pre-entered in SAP Enterprise Buyer)
Please award the points if it helps.
BR,
Vijay Mittal

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

Function module for offline vendor creation.

Hi Xperts,
I have searched all threads but i didn't find it, plz help me its urgent,
Is there a Function Module or BAPI for vendor creation. The BAPI_VENDOR_CREATE works online. I am looking out for an offline. This is for avoiding the use of BDC that we are currently using.
thanx in advance
Regards,
Naresh.

Hey whats up xperts............

Need Sample Code for Vendor creation using JAVA API

Hi,
I have a scenario like Vendor creation using Java API.
1.I have Vendors (Main) Table.
2.I have look up tables like Account Group.
3.Also Qualifier table(Phone numbers) too.
Could you please give me the sample code which helps me to create Vendor records using Java API?
I need Code samples which should cover all of the above scenario.
Marks will be given for the relevent answers.
Best Regards
PK Devaraj

Hi Devraj,
I hope the below code might solve all your problem:-
//Adding Qualified field
//Creating empty record in Qualifed table
//Adding No Qualifiers
Record qualified_record = RecordFactory.createEmptyRecord(new TableId(<TableId>));
try {
qualified_record.setFieldValue(new FieldId(<fieldId of NoQualifier), new StringValue(<StringValue>));//Adding No Qualifier
catch (IllegalArgumentException e2) {
// TODO Auto-generated catch block
e2.printStackTrace();
catch (MdmValueTypeException e2) {
// TODO Auto-generated catch block
e2.printStackTrace();
//Creating Record in Qualified table
CreateRecordCommand create_command = new CreateRecordCommand(connections);
create_command.setSession(sessionId);
create_command.setRecord(qualified_record);
try
create_command.execute();
catch(Exception e)
System.out.println(e.toString());
RecordId record_id = create_command.getRecord().getId();
//Adding the new record to Qualifed Lookup value and setting the Yes Qualifiers
QualifiedLookupValue lookup_value = new QualifiedLookupValue();
int link = lookup_value.createQualifiedLink(new QualifiedLinkValue(record_id));
//Adding Yes Qualifiers
lookup_value.setQualifierFieldValue(0 , new FieldId(<FieldID of Yes Qualifier>) , new StringValue(<StringValue>));
//Now adding LookUP values
//Fetch the RecordID of the value selected by user using the following function
public RecordId getRecordID(ConnectionPool connections , String sessionID , String value , String Fieldid , String tableid)
ResultDefinition rsd = new ResultDefinition(new TableId(tableid));
rsd.addSelectField(new FieldId(Fieldid));
StringValue [] val = new StringValue[1];
val[0] = new StringValue(value);
RetrieveRecordsByValueCommand val_command = new RetrieveRecordsByValueCommand(connections);
val_command.setSession(sessionID);
val_command.setResultDefinition(rsd);
val_command.setFieldId(new FieldId(Fieldid));
val_command.setFieldValues(val);
try
 val_command.execute();
catch(Exception e)
RecordResultSet result_set = val_command.getRecords();
RecordId id = null;
if(result_set.getCount()>0)
 for(int i = 0 ; i < result_set.getCount() ; i++)
 id = result_set.getRecord(i).getId();
return id;
//Finally creating the record in Main table
com.sap.mdm.data.Record empty_record = RecordFactory.createEmptyRecord(new TableId("T1"));
try {
 empty_record.setFieldValue(new FieldId(<FieldId of text field in Main table>),new StringValue(<StringValue>));
 empty_record.setFieldValue(new FieldId(<FieldId of lookup field in Main table>), new LookupValue(<RecordID of the value retrieved using the above getRecordID function>));
empty_record.setFieldValue(new FieldId(<FieldId of Qualified field in Main table>), new QualifiedLookupValue(<lookup_value>));//QualifiedLookUp value Retrieved above
} catch (IllegalArgumentException e1) {
// TODO Auto-generated catch block
 e1.printStackTrace();
} catch (MdmValueTypeException e1) {
 // TODO Auto-generated catch block
 e1.printStackTrace();
//Actually creating the record in Main table
CreateRecordCommand create_main_command = new CreateRecordCommand(connections);
create_main_command.setSession(sessionId);
create_main_command.setRecord(empty_record);
try
 create_main_command.execute();
catch(Exception e)
 System.out.println(e.toString());
Thanks
Namrata

Employee vendor creation

Hi ,matically
how to create automatic vendor creation via PRAA.
Is this prgm can run in back ground and will updat enewly hired employees automatically.
GK

Hi GK,
Yes this can be done.
Follow the steps mentioned in this doc - http://scn.sap.com/docs/DOC-27098
Thanks
Vipin

Vendor creation process

Similar Messages

Maybe you are looking for