Address Title for Vendor Replication

Hi experts!
Vendor in R/3 has no value in the 'Title' field of the address. When we replicate the same to SRM the 'Title' field is maintained with value '0003 Company'.
From OSS-Note 674481 - BBPGETVD/BBPUPDVD: Problems with form of address texts
I can read that a standard code for organizations is taken as default, if no address title is maintained. Does anyone of you know whether we can influence this behaviour? We would like to have the title the same way as in R/3. If it is empty it should also be empty in SRM.
Many thanks for your help.
Best regards,
Corinne

Hi
Which SRM and R/3 versions are you using ?
Please go through the following SAP OSS Notes, which will help ->
Note 738777 Problems with form of address text during transfer from UME
Note 674481 BBPGETVD/BBPUPDVD: Problems with form of address texts
Note 452017 Business partner maintenance: 'blank' form of address text
Note 503318 Update of e-mail addresses of the R/3 Backend vendors
Note 487420 Replicating the vendors as a job in EBP 2.0
Note 518531 EBP: Update with terms of payment fails
Note 456967 'Dun & Bradstreet' number, EBP 3.0
Note 361829 EBP (BBP2.0C): Business partner <-> vendor mapping
Note 357201 BBP 2.0B: Business partner <--> vendor mapping
Note 340227 Ext. business partner: address texts are not dynamic
Note 407800 Converting SU01 users to EBP users
Note 419423 Repairing incorrect EBP users
Note 330957 Creating user via BBPUSERMAINT causes error
Do let me know.
Regards
- Atul

Similar Messages

In what case, we need to use PI for vendor replication in MM-SUS?

Dear Experts,
In what scenarios, we need to use or configure the PI settings for vendor replication between MM and SUS? The SAP configuration guide for SRM 7.01 mentions about the PI settings for vendor replication from ECC to SUS.
However, we are able to replicate the vendor from ECC to SUS using the program BBPGETVD in SUS client?
In what circumstances, we need to configure the PI settings for vendor replication when we are able to do so in a much simpler way?
Thanks in advance,
Ranjan
Ranjan Sutradhar

Hi Ranjan,
In all circumstances you need to replicate vendors from MM to SUS via PI. BBPGETVD is not the right way to replicate vendors to SUS because the information like vendor class, assignment of this vendor class to an object and the vendor classification cannot be transferred via BBPGETVD.
Hence you will have to use PI. You can try sending a PO from MM to SUS and the PO will fail in SUS with a message like 'Vendor not present in SUS' if you use BBPGETVD.
Regards,
Nikhil

XML message failing in the SUS side for vendor replication from ERP

Dear Experts,
We have configured MM-SUS scenarios in our environment of SRM 7.01/ECC 6 ehp 5.
We are trying to replicate the Vendor master from ECC to SUS using PI ( idoc message ZCREMAS_SUS_MM)).
The message is successully processed in the PI. It is failing in the SUS side.
The exception is as below:
An error occurred when deserializing in the simple transformation program /1SAI/SASF5486DA19E3520591A1B (Length of "123 JALAN TIMUR" exceeds maximum length "10", specified with tt:maxLength Kernel ErrorId: ST_CONSTRAINT_MAXLENGTH) XML Bytepos.: 607 XML Path: ns0:SupplierPortalTradingPartner(1)TradingPartnerOrganization(2)Address(8)HouseNumber(6) An error occurred when deserializing in the simple transformation program /1SAI/SASF5486DA19E3520591A1B Length of "123 JALAN TIMUR" exceeds maximum length "10", specified with tt:maxLength</SAP:Stack>
Where I can change the settings to allow the maximum length of 10?
Any input will be highly appreciated.
Thanks and regards,
Ranjan

Hi,
Note 1510484 - SUS: Order longtext in message area displayed incorrectly
Note 1559121 - SUS: Long texts are getting broken in PCO (POR)document
Given notes are not exactly related to the problem. Let me know if notes could work for the current issue.
Regards,

Address comparison to avoid duplicates in Vendor replication

Dear SRM experts,
Can you please enlighten me about the Address Comparison check in Vendor replication?
What would be the consequences of running the vendor replication without checking the address comparison?
Thanks,
Vipra.

Hi SG,
Sorry for the wrong description, you are correct it works the other way round.
The vendors we are trying to replicate does not exist in the system yet, still we have to uncheck the option beofre replicating them.
There should be no problem even after selecting the cbox..right? because the vendors are new?
Why is it giving error for new vendors?
Thanks for the help,
Anubhav

Maintain multiple address for vendor

User purchase article from vendor A at addess#1 but returned article back to vendor A via address#2. Vendor has 2 different departments handling delivery and returns.
How can I configure 2 adddress for the same vendor code?
If I had to used a partner function, what suggested partner function should I used?
My PO order entry currently only accept vendor code.
Suppose I need to add in a partner, like sold-to and ship-to in SD, is there a way to configure the screen?
Where do I do it.
Thanks
bye

Hi Colin,
What is the bussiness reason for multiple addresses for the same vendor?
If the vendor maintains several different physical locations at different addresses, then they should be created as different vendor master records. Then, if they all use the same payment office, they can be partnered to the same invoicing vendor.
If you need to add a seperate address for the supplier location, payment location, billing location, etc, then you must create each of them using the correct account group and use partnering to tie them all together.
Also, there is a way to maintain multiple addresses for the same vendor - but this is used for maintaining different international versions of the same address. (See the international button) - which requires some configuration in central address management.
Or,
Go for one-time-vendor concept else it is not possible .
Also,
Partner function can be used to maintain different address.
This is the advantage of keeping the partner function in vendor account groups.
You create different vendor codes for different addresses and assign the same.
Regards,
Rahul.

Datasource for Vendor Contact person Address

Hi,
I am looking out for the DS for Vendor Contact person address, which is taken from ADRC table. 0BP_DEF_ADDRESS_ATTR is having Business partner number. it gives all the required data. how to i link it with vendor LFA1 and COntact PErson in KNVK to get the required result.
Thanks & regards
Abi

Hi,
There is no standard data source available for your requirement.
You can enhance 0Vendor_attr master data with LFA1-ADRNR, KNVK-PARNR and address fields in ADRC and populate using user exit code based on the following logic.
Get LFA1-ADRNR where 0VENDOR_ATTR-LIFNR = LFA1-LIFNR
Get KNVK-PARNR where LFA1 - KUNNR = KNVK - KUNNR
Get address fields from ADRC where
LFA1 - ADRNR = ADRC - ADDRNUMBER
ADRC - DATE_FROM = Hard code the values required
ADRC - NATION = Hard code the values required eg. I for international version.
Hope it helps
Regards, Jeya

Vendor details address table for streets

Hi,
Can any one tell me the table name for vendor adrress details for STREET1 STREET2??
thanks in advance.
cheers!!
biswajit.

Hi
Try ADRC table in SE16 but u need a address number to get data which is available in LFA1 table as ADRNR field
now u will be able to fing street address with respect to vendor
If required u can club these reports to develop query take help from abaper
Vishal....

User exit to change vendor e-mail address used for PO output via e-mail...

We have two vendor e-mail addresses for a particular vendor. Ignoring output determination, it looks like I will need to control which of the two e-mail vendor addresses is used when the PO is output via e-mail.
The default is the first one e-mail address, but for PO's I would like to force the second vendor e-mail address.
There are tonnes of exits available for PO output by the looks of it so I am trying to discover which is relevant for what I am trying to achieve.
Jas
Edited by: Jason Stratham on Apr 30, 2009 5:53 PM

Thanks Martin,
I guess that's the same path that I took earlier when using SPRO and looking at the Purchasing->Messages. In my case it's ZMEDRUCK, but that does not help me in regards to controlling the vendors e-mail address being used. When sending the PO as an e-mail it uses (by default) the first e-mail address of the Vendor, whereas the vendor could have multiple ones. In my test case my vendor has two addresses but it always defaults to using the first. I know that I need to modify this behaviour somehow, but how I have no idea as I can find no Exit routine.
Jas

Different addressed for Vendors

As per the requirement from the client we want to have 2 diff. vendor addresses.
On one address the vendor cheque is sent and on another regular corresponce is done.
Is it possible to have 2 diff. address in Vendor master records?
Regards,
Vaibhav

Hi,
You need to have two vendor codes, with different addresses, maintain the vendor code with the address to which cheque needs to be printed as invoicing party in the partner function of the VMR,
eg - Vendor code 1001 - with ordering address
Vendor Code 1002 - with invoicing address
Now go the VMR of 1001 and change the invoicing party to 1002 in the parter function tab.
Now the PO will be created with 1001, all ordering correspondence will go with the ordering address and the corresponding cheque will be printed with the invoice address..
Vendor 1002 can be created only at the Company code level, so that, it can not be used for procurement even by oversight.
Trust this will suffice your requirement
Regards
Merwyn

Internation Address Version for Customer and Vendor Master

Hi Everyone,
There are a few fields on the General Data screen which are overwritten by value in the International address version and vice-versa. I am listing these fields below and I would like to know if this is just standard SAP functionality or did something change in our system after upgrading to ECC 6.0.
Communication Language
Postal code
Telephone
Mobile phone
Fax number
Email address
Thanks for your help!
Sheetal

I would assume that this is standard functionality, as e.g. it does not really make sense to have different communication languages in the address versions. It is just the opposite: if you have two address versions (e.g. standard and kanji) it is quite important to stored the information about which is the preferred communication language of the customer.
Regards
Martin

Vendor Replication

Hi All,
When I try to replicate vendors, I follow this steps..
I log on NEP and go to Transaction /nBBPGETVD...
Screen Name = Transfer Vendor Master Records
Fill in the following table entries
Table = Identification of Source Data
Fields
System = BPAMANDxxx
Limit Vendor Selection:
Vendor From = xxx (See list Preferred Supplier Vendor List.xls)
Purchasing Organization From = xxx
Table = Organizational Unit for Vendor
Fields
Object ID = xxxx (see Vendor Org Group folder for ID)
Click on button to stage transmission.
Click on Display list button to view
New window will display results
Title = Valid External Vendor Description
Review list and when finished click on Cancel (F12) Icon
If ready click on Start Transmission button
Click on Continue (Enter) Icon to continue
To view application log.
I go to transaction SLG1
Add time range if needed then click the Execute (F8) icon
But when I execute transaction SLG1 I get the following message:
'' Error Changing Business Partner (data) Module: BBP_BUPA_GET_NUMBER Vendor : xxxxxxx ''...
Please, let me know is you know what the problem is...
Thanks in advance!!
Yanina.

Hi
When this problem is happening ?Which SRM and R/3 versions are you using ? 
See the more Related links ->
Re: Vendor Replication
Vendor replication Error. SAP R/3 to EBP system
Re: "Partner function may not be changed"
Error Changing Business partner address
"Partner functions may not be changed"
Re: Unable to replicate the Vendor Master Records
See SAP OSS Note 962474 - Error after changing partner data
Please go through the following SAP OSS Notes as well ->
Note 794653 - SRM Partner maintenance:possible loss of data in error case
Note 904550 - Obsolete vendor in document preview of the sourcing cockpit
Also try to have full authorization for doing this operations.You can maintain this in Personalization Tab in Trasaction PFCG for the specific Role.
Do let me know.
Regards
- Atul

Tables for vendor invoice and payment

Hi Gurus.
I want to know from which tables i can get the information for folllowing points.
1. Vendor Invoices - Complete (Header and Item)
2. Vendor Payments Details Detail about payment method (check, wire, etc)
Please tell me tje table names.

There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
|Table Name |Table Description |
|/BEV3/CHKOMPAZVV |Append Structure CH -> CO PA |
|/CWM/ACCIT |Append Structure for Enhancement of Structure ACCIT in CWM |
|/CWM/KOMP |Catch Weight Management Enhancement |
|/DSD/TAXJURCD |Ship From Tax Jurisdiction Code: for Header Prc Comm Str |
|/SAPNEA/J_SC_LFA1 |Subcontractor Information |
|/SAPNEA/J_SC_LFB1 |Subcontracting Management |
|/SAPPSPRO/A_FI2_LONGNUM |IBU-PS: Append structure for structure NONBSEG |
|/SAPPSPRO/A_LONGNUMBER |additional fields for SPIIN number |
|/SAPPSPRO/EADD |Purchasing Document Header: Additional Data |
|/SAPPSPRO/EADD_DATA |Purchasing Document Header: Data Part Additional Information|
|/VSO/R_KNA1_A |Append to KNA1 for Vehicle Space Optimization |
|/VSO/R_KNA1_I |Additional Data for Vehicle Space Optimization for KNA1 |
|AACCHD_FMFG |US federal fields |
|AACCHD_PSO |IS-PS: ACCHD Append Structure for Payment Requests |
|AACCIT_GM |Append for Grants Management |
|AACCIT_PSO |IS-PS: ACCIT Append Structure for Payment Requests |
|AACCIT_SSP |Append for Payment Statistical Sampling Process |
|AACCIT_USFG |Append structure for US federal government |
|AAUSZ_CLR_USFG |Clearing information for US Fed (Tresury Confirmation) |
|ABKPF_PSO |IS-PS: BKPF Append Structure for Payment Requests |
|ABKPF_UMB |IS-PS: Append Structure for Transfer Transaction FMITPO |
|ABSID_PSO |IS-PS: Data appendix of open items customers |
|ABSIK_PSO |IS-PS: Data appendix of open items vendors |
|ABSIS_PSO |Local Authorities |
|ABUZ |Help Structure for Line Items to be Generated Automatically |
|ACCCR |Accounting Interface: Currency Information |
|ACCCR_FKEY |Key: Acctg Currency Data for Line Item Including Currency |
|ACCCR_KEY |Key: Accounting Currency Data for Line Item |
|ACCFI |Interface to Accounting: Financial Acctg One-Time Accts |
|ACCHD |Interface to Accounting: Header Information |
|ACCHD_KEY |Key: FI/CO Document Header |
|ACCIT |Accounting Interface: Item Information |
|ACCIT_EXTENSION |ACC Document: Additional Item Information |
|ACCIT_JV |Joint Venture Accounting |
|ACCIT_KEY |Key: FI/CO Line Item |
|ACCIT_WT |Withholding tax information for FI Interface |
|ACCRDF |Fields for Posting Small Differences: Preparation |
|ACC_DOCUMENT |Accounting document |
|ACC_KONTEXT |Context Info for FI Single Screen Transactions FB50 and FB60|
|ACERRLOG |Return Parameter |
|ACGL_HEAD |Fields for Document Header Entry Screen |
|ACGL_ITEM |Structure for Table Control: G/L Account Entry |
|ACSCR |Communication Structure for Field Modification SAPLFDCB |
|ACSPLT |Carrier for Split Information re: Current Account Line Items|
|ACSPLT_WTNEW |Proportion of New Withholding Tax |
|ACSPLT_WTOLD |Proportion of Old Withholding Tax |
|ADDR1_SEL |Address selection parameter |
|AEBPP_KNBK |Additional Fields Bank Data Biller Direct |
|AEBPP_LFBK |Additional Fields Bank Data Biller Direct |
|AFMIOI |Append for new fields ECC50/ERP |
|AFMIOI_USFG | SD order needs quantity |
|AFMISPS |Additional Fields for Table FMISPS |
|AFM_ACCIT_EXTENSION |Extension for FM Payment Update |
|AFM_FAGL_GLT0_ACCIT_EXT |Extension FM Account Assignments |
|AFM_FI_BKPF_SUBST |Append to Structure BKPF_SUBST |
|AFM_FMFCTF |Append for Fund Center substrings |
|AFM_FMFINCODE |Append for Fund substrings |
|AIFM01D |Append for IFM01D |
|AKNA1_FMFG |US Federal Government Customer Master Data Additional Fields|
|AKNA1_PSO |Local Authority Additional Fields |
|AKNB1_PSO |IS-PS: Customer Master Record, Additional Data (Co.Code) |
|AKNBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALFA1_FMFG |US Federal Government Vendor Master Data Additional Fields |
|ALFA1_PSO |Local Authority Additional Fields (Address) |
|ALFB1_FMFG |PS fields for company code-specific master data field |
|ALFB1_PSO |IS-PS: Data Appendix Vendor Master Record (Company Code) |
|ALFBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALVDYNP |ALV dialog screen fields |
|ALV_S_FCAT |Field Catalog (for LVC and for KKBLO) |
|ALV_S_FILT |Filter Criteria (for LVC and for KKBLO) |
|ALV_S_GRPL |Group Levels (for LVC and for KKBLO) |
|ALV_S_LAYO |Layout (for LVC and for KKBLO) |
|ALV_S_PCTL |Structure for Checking Print in ALV |
|ALV_S_PRNT |Print settings (for LVC and KKBLO) |
|ALV_S_QINF |Structure for Quickinfos of Exceptions |
|ALV_S_SGRP |Field Groups (for LVC and for KKBLO) |
|ALV_S_SORT |Sort Criteria (for LVC and for KKBLO) |
|ANBZ |Help structure for asset line item |
|ANLZACCOUNT |Additional Account Assignment Objects in Asset Accounting |
|ANLZACCOUNT_FKBER |Account Assignment Objects: ANLZACCOUNT with Function Added |
|ARC_PARAMS |ImageLink structure |
|AT003_XBLNR2 |Append structure for US federal government |
|AUSZ1 |Clearing Table 1 |
|AUSZ2 |Clearing Table 2 |
|AUSZ_CLR |Assign Clearing Item to Cleared Items |
|AUSZ_CLR_ASGMT |Assgt of Clrg Items - Cleared Items with Acct Assignment |
|AUSZ_INFO |Open item data for clearing transactions |
|AVBKPF_FMFG |US federal |
|AVBKPF_PSO |IS-PS: Append Structure VBKPF for Payment Requests |
|AVBSEGDPSO |IS-PS: Append Structure VBSEGD for Payment Requests |
|AVBSEGKPSO |IS-PS: Append Structure VBSEGK for Payment Requests |
|AVIK |Payment Advice Header |
|AVIP |Payment Advice Line Item |
|BALHDR |Application log: log header |
|BALMT |Application Log: Structure for a formatted message |
|BAL_S_CLBK |Application Log: Return routine definition |
|BAL_S_CONT |Application Log: Context |
|BAL_S_MSG |Application Log: Message Data |
|BAL_S_PAR |Application Log: Parameter Name and Value |
|BAL_S_PARM |Application log: Parameters |
|BAPIASCONT |Business Document Service: File Content ASCII |
|BAPIBDS01 |Business Document Service: Reference Structure for BAPIs |
|BAPICOMFIL |BDS: Command File for Transport Entries |
|BAPICOMPO2 |SBDS: Enhanced Component Information |
|BAPICOMPO3 |SBDS: Enhanced Component Information |
|BAPICOMPON |Business Document Service: Component Table |
|BAPICONNEC |BDS: Structure for BDS Links |
|BAPICONTEN |Business Document Service: File Content |
|BAPIDPROPT |BDS: Structure for Properties |
|BAPIFILES |Business Document Services: Transfer Table for File Names |
|BAPIPROPER |BDS: Structure for Properties |
|BAPIPROPTL |BDS: Structure for KPRO Properties |
|BAPIQUERY |BDS Structure for Query Table |
|BAPIRELAT |Business Document Service: Relations |
|BAPIRET1 |Return Parameter |
|BAPIRETURN |Return Parameter |
|BAPISIGNAT |Business Document Service: Signature Table |
|BAPISRELAT |Business Document Service: Relationship Table with Signature|
|BAPIURI |Business Document Service: URI Table |
|BDCMSGCOLL |Collecting messages in the SAP System |
|BDCRUN |Batch input: Runtime analysis |
|BDIDOCSTAT |ALE IDoc status (subset of all IDoc status fields) |
|BDI_SER |Serialization objects for one/several IDocs |
|BDN_FKT |Business Document Navigator: Functions to be Excluded |
|BDWFAP_PAR |Parameters for application function module - IDoc inbound |
|BDWFRETVAR |Assignment of IDoc or document no. to method parameter |
|BDWF_PARAM |Parameters for workflow methods for IDoc inbound processing |
|BKDF |Document Header Supplement for Recurring Entry |
|BKDF_SUBST |Process Interfaces: Substitutable fields during posting |
|BKORM |Accounting Correspondence Requests |
|BKP1 |Document Header Supplement for Update |
|BKPF |Accounting Document Header |
|BKPFBU_ALV |Document Overview: Display Document Headers in ALV Grid Ctrl|
|BKPF_CARD |Credit Card: Append for BKPF |
|BKPF_LINE |Item Category for XBKPF_TAB |
|BKPF_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BKPF_USFED |Append structure for US federal government |
|BLNTAB |Document Number Table for Financial Accounting |
|BNKA |Bank master record |
|BNKAAPP |Appendix to Table BNKA |
|BNKT |Conversion of temporary to internal bank keys |
|BOOLE |Boolean variable |
|BSEC |One-Time Account Data Document Segment |
|BSEC_LINE |Item Category for XBSEC_TAB |
|BSED |Bill of Exchange Fields Document Segment |
|BSEE |Changeable Fields in the Line Item |
|BSEG |Accounting Document Segment |
|BSEGL |Document Segment: Fields Derived for Line Layout Variant |
|BSEGS |G/L Item Transfer Structure for Single Screen Transactions |
|BSEGT |Transfer Table for the Tax Postings to be Generated |
|BSEGZ |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
|BSEG_ALV |Document Overview: Document Item Display in ALV Grid Control|
|BSEG_LINE |Item Category for XBSEG_TAB |
|BSEG_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BSET |Tax Data Document Segment |
|BSEU |Line Item Additional Information (Update) |
|BSEZ |Line Item Additional Information (Online) |
|BSEZ_LINE |Line Item Category for XBSEZ_TAB |
|BSID |Accounting: Secondary Index for Customers |
|BSIK |Accounting: Secondary Index for Vendors |
|BSIP |Index for Vendor Validation of Double Documents |
|BSIS |Accounting: Secondary Index for G/L Accounts |
|BSIX |Index table for customer bills of exchange used |
|BTXKDF |Fields for Exch.Rate Difference Posting for Taxes |
|BVOR |Intercompany posting procedures |
|CACS_A_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_A_CUST_COND |Commissions: Customer Fields Condition Technique |
|CACS_A_FIELDSPRICING |Append for Condition Technique Fields from Commission System|
|CACS_S_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_S_CUST_COND |Condition Attributes |
|CACS_S_FIELDSPRICING |Comm.: All Condition Technique-Relevant Commission Fields |
|CACS_S_FSINS |Customer Fields for Condition Technique of Insurances |
|CCDATA |Payment cards: Database fields relevant to both SD and FI |
|CFW_LINK |CFW: Link Info of a Container |
|CI_COBL |Extension |
|CKI_ACCIT_ML |Transfer from MM to ML in accit-structure |
|CNTLSTRLIS |Control stream list |
|COBK |CO Object: Document Header |
|COBK_ONLY |Non-key fields only in COBK (INCLUDE structure) |
|COBL |Coding Block |
|COBLF |Coding block: Tax table structure |
|COBL_COKZ |Assignment types for CO account assignments |
|COBL_DB_INCLUDE |Include with Additional Account Assignments for DB Tables |
|COBL_EX |Coding Block for External Applications (Not CO/FI) |
|COBL_FI |Fields from COBL that Must not Be Overwritten in FI |
|COBL_FM |Additional Fields for FM |
|D010SINF |Generated Table for View D010SINF |
|D020S |System table D020S (screen sources) |
|D020T |Screen Short Description |
|DBSEG |Dialog Supplementation BSEG (Taxes) |
|DD02L |SAP Tables |
|DD03P |Structure |
|DD03V |Table fields view |
|DD07V |Generated Table for View DD07V |
|DD23L |Matchcode ID |
|DD32P |Interface structure for search help parameters |
|DDSHDEFLT |Description of a default value for search help fields |
|DDSHDESCR |Interface: elementary search helps of a search help |
|DDSHFPROP |Characteristics of search help parameters |
|DDSHIFACE |Interface description of a F4 help method |
|DDSHRETVAL |Interface Structure Search Help <-> Help System |
|DDSHSELOPT |Selection options for value selection with search help |
|DDSUX030L |Nametab Header, Database Structure DDNTT |
|DDSUX031L |Nametab Structure, Database Structure DDNTF |
|DDTYPES |Table of all Dictionary types and classes |
|DFIES |DD Interface: Table Fields for DDIF_FIELDINFO_GET |
|DISVARIANT |Layout (External Use) |
|DOKHL |Documentation: Headers |
|DPPROPS |General property structure for data provider |
|DTC_S_LAYO |Structure for Design of Double Table Control |
|DTC_S_TC |Structure for table controls in the double table dialog box |
|DTC_S_TS |Tab Title Structure |
|DYNPREAD |Fields of the current screen (with values) |
|E071 |Change & Transport System: Object Entries of Requests/Tasks |
|E071K |Change & Transport System: Key Entries of Requests/Tasks |
|EAPS_20 |Field Enhancements for EA-PS 2.0 |
|EDIDC |Control record (IDoc) |
|EDIDS |Status Record (IDoc) |
|EDIFCT |IDoc: Assignment of FM to log. message and IDoc type |
|EDIMESSAGE |Transfer Structure with all Sy Fields for T100 |
|EDI_DS |Status record for interface to EDI subsystem |
|EDI_HELP |Help Structure for Reference Fields in EDI Function Groups |
|EK05A |Communication Area Purchasing - Financial Accounting |
|ESKN |Account Assignment in Service Package |
|EUDB |Development Environment Objects |
|EUOBJ |Workbench: Development Objects |
|EXCLTAB_LINE |Lines of EXCLTAB with OK Code to be Deactivated |
|EXISTING_DOC |Original Document |
|F05ACTRL |Control Fields for SAPMF05A and Subprograms |
|FAGLBSEGL_S |Additional Sender Flds from General Ledger for Doc. Overview|
|FAGL_GLT0_ACCIT_EXT |Line Information for Document Splitting |
|FAGL_MIG_S_BUKRS_LEDGER |Combination of Company Code and Assigned Ledgers |
|FAGL_SPLIT_FLD_S |Characteristics Permitted for Split |
|FAGL_S_APPLICATION |Application and Subapplication |
|FAGL_S_BALDIM |G/L Characteristics of Document Split in New General Ledger |
|FAGL_S_BUKRS |Structure with Company Code |
|FAGL_S_BUKRS_EXT |Structure: Company Codes --> Ledgers |
|FAGL_S_CURTYPES |Currency Types of a Ledger |
|FAGL_S_MIG_001 |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S |
|FAGL_S_MIG_MGPLN_EXT |Structure: Extended Migration Plan Information |
|FAGL_S_T8G40_BS |Split Fields with Characteristic "Balance Sheet" |
|FCRD_VBKPF |Credit Card: Include for Appends for BKPF, VBKPF |
|FCRD_VBSEG |Include for Appends for VBSE* |
|FDM_AR_CASE_ATTR_1 |FSCM DM: |
|FDM_AR_LINE_ITEM |FSCM: DM |
|FDM_AR_RFPOS |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
|FELD |Screen Painter fields (internal) |
|FICCO |Adjustment Values for External Document Items |
|FICCT |Totals Information for Interclient Posting |
|FICTX |Tax Information for ICT |
|FIELDINFO |Field attributes for a specific field |
|FIN1_PARAM |OBNG: Trans. structure for official doc. numbering (global) |
|FIN1_PARAM_FI |OBNG: FI parameters |
|FIN1_PARAM_MM |OBNG: MM Parameters |
|FIPEX_STRUC |Subfields Commitment Item |
|FIPOEXT |Help structure for line items to be generated automatically |
|FIREVDOC |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS |
|FISTL_STRUC |Substructure Fund Center |
|FM01 |Financial Management Areas |
|FMBLSTRING_COMPONENTS |Component of the BL String |
|FMCI |Commitment items master data |
|FMDY |FIFM: Screen Fields |
|FMFCTR |Funds Center Master Record |
|FMFG_ACCIT_EXTENSION |Extention for all fields that have to be transfered into BL |
|FMFINCODE |FIFM: Financing code |
|FMFPO |FIFM: Commitment Item |
|FMHRBA_NEG_DOC_TYPES |HR Integration: Doc. Types for Negative Funds Commitments |
|FMHRBA_SETTINGS |Integration with HR: Settings |
|FMHRBA_VAD_SETTINGS |HR Integration: Generate Value Adjustment Docs for Changes |
|FMICCN |FM: Append Structure for FMIOI (CCN Fields) |
|FMIDATA |Common Data for Funds Management Actual Data |
|FMIDATAFI |Clean FI Data for Funds Management Actual Data |
|FMIDATAOI |Clean Open Item Data for Funds Management Actual Data |
|FMIFIIT |FI Line Item Table in Funds Management |
|FMIKEY |Common Key for Funds Management Actual Data |
|FMIKEYFI |FI - Key for Funds Management Actual Data |
|FMIKEYOI |Common Key for Funds Management Actual Data |
|FMIOI |Commitment Documents Funds Management |
|FMIOIKEY |Key for Table FMIOI |
|FMIOI_USFG | SD order needs quantity |
|FMIREF |Ref. Funds Management Actual Data to Preceding Document |
|FMISPS |General Parameters for Funds Management |
|FMIT |Totals Table for Funds Management |
|FMMRESERV |Include for the Reduction of Funds Reservations (FM) |
|FMRFC |Function Modules and their RFC Destinations |
|FMSP_SPLIT_FIELDS |PSM Fields used in multiple account splitting |
|FMT001 |Additional Customizing for Funds Management |
|FMUP00T |Update Profiles |
|FMUP01 |Update Control with Value Type Dependency |
|FMUP_INV_KEY |Extension for FM Update: FI Key of Invoice |
|FMUP_PAY_KEY |Extension for FM Update: FI Key of Payment |
|FS006 |Fields for Optical Archiving |
|FTCHECK |Foreign Trade: Import Simulation - Ctrl Fields for Pricing |
|FTEXTS |Communication Structure for Additional Components |
|FTGENERAL |Foreign Trade: General Fields Item |
|FUND_STRUC |Substructure Fonds |
|FVD_TZB0A |Append to TZBOA: Loans Fields |
|GLACCOUNT_CCODE |G/L Account Master Record: Company Code |
|GLACCOUNT_CCODE_DATA |G/L Account Master Record: Company Code - Data |
|GLACCOUNT_CCODE_INFO |G/L Account Master Record: Company Code - Information |
|GLACCOUNT_CCODE_KEY |G/L Account Master Record: Company Code - Key |
|GLX_ORG_INFO |Organizational Assignment |
|GMBSEGZ |Grants Management Add-on |
|GXXLT_H |XXL interface: horizontal features |
|GXXLT_O |XXL_interface: texts for online display |
|GXXLT_S |XXL interface: structure of the semantics table |
|GXXLT_V |XXL interface: vertical features |
|HELPVAL |Restrict Value Range - Transfer Table |
|HELP_INFO |Transfer Values for the Help Processor |
|HELP_VALUE |Structure or Function Module HELP_VALUE_GET_FOR_TABLE |
|HHM_COBL |Include for COBL from FM |
|IADDR_PSO |Local Authority Additional Fields (Address) |
|IBKPF_PSO |IS-PS: Include Structure BKPF Payment Request Doc.Header |
|ICDIND |Structures for generating change document update programs |
|ICON |Icons table |
|ICONS |Icons |
|ICURR |Interface for Currency Translation

MM-SUS Scenario - Issue in vendor replication

Hi Gurus,
We are implementing MM-SUS scenario on SRM 7.0 interacting with a system R/3 4.6C and NW PI 7.0.
Now we are workking on the vendor replication from R/3 by mean tx BD14. So we performed all neccesary configuration and functional steps on R/3 system and on SRM to be able to execute BD14
After execution we obtain messages about succesfully IDoc creation for vendor data transmission and we see in tx WE02 that everything was OK, current status=03 (data passed to port OK).
But when we login on SRM, we dont' found the correspondent business partner in tx. BP and neither his connection with central vendor group in tx PPOMV_BBP and user/password generation to be sended by automatic email to supplier.
Can anybody help me with this issue?.Thanks in advance.
Regards,
Horacio

Hi,
We have been investigated the issue and for some similar issues the procedure to
delete the entried in VENMAP table and after to do the replication again
have solved the issue.
The steps to delete the entry from VENMAP:
- Goto to transaction SE16
- Open 'VENMAP' table
- Type in the vendor number under 'VENDOR_NO' field, which you
   need to delete.
- Select the record and open in display mode (or just double
   click on the record)
- In the 'Table VENMAP Display' screen, on the transaction bar,
   type '/h' and press enter.
- Click on the screen and press enter.
- You will be in the debug mode. Change the 'code' value to 'DELE'.
- Press F8 and execute the program. Now you will find a 'Delete Entry'
   button.
- Click on the 'Delete Entry' button and remove the entry from VENMAP.
Once this is done, run BBPGETVD transaction and unset 'Address
Comparison to Identify Duplicates'.
We can do other test, Would it be possible to you enter the supplier
data to the BUT000 table manually for the currupted business Partener ?
Partner GUID, Partner can be taken from the VENMAP table.
Please test both procedure and update me if it solve the issue for
the Partner.
Please check the note 548862 FAQ: EBP user administration, topics 2
and 3 about how you can check all EBP users and about BUP_BUPA_DELETE.
We hope this information can help you.
Kind Regards,
Edel.

Vendor Replication not Successful in EBP4.0 from ECC R/3 4.7

Hi,
I am trying to replicate vendors from my ECC backend using BBPGETVD.
I have specied the backend system , vendor number and the object ID of the organizational unit for Vendor. I have checked the Only transfer R/3 numbers option. When I click on the 'Start Transrer' button , I go to the next screen where I find the total number of Vendors as 1 and Adoption of R/3 description as 1. After this when I click the 'Start Transmission' button , I get the message Replication program started but the log does not show any entries for the same and the vendor is not getting replicated.
If anyone has come across the same , then let me . Helpful answers/solutions will be rewarded points accordingly.
Regards,
Kalyan

Hi,
Could you see anything in PPOSV_BBP txn under your Vendor Group ( Vendor Root Org) ?
Also check the tables VENMAP ,VEN000 tables whether the vendor has been replicated.
Also is the vendor already replicated in SRM ?
See these notes:
392446- old naote- All r/3 numbers are already assigned.
973404- Address data not transfered correctly.
BR,
Disha.

Partner functions OA and IP missing for Vendor in Extended classic PO

As part of current Classic scenario, we have maintained OA (Ordering Address) and PI (Invoicing Party) for a vendor in R/3. We have also maintained different ordering addresses for multiple plants in the Vendor master: Partner functions screen --> Alternative data.
I would like to acheive the same functionality in Extended Classic scenario. We have replicated the vendors from R/3 to SRM. After activating Extended Classic scenario, we see only VN as the partner function in R/3 PO.
Q1. How can we enable OA and PI partner functions in R/3 PO (Extended Classic) ?
Q2. How can we enable different ordering addresses for multiple plants in R/3 PO (Extended Classic) ?

Hi
Which SRM Server are you using ?
You need to maintain Partner Functions in the SRM Server - SPRO Transaction - Configuration Settings.
Here is the Path from SPRO Transaction ->
Supplier Relationship Management -> SRM Server -> Cros Application Basic-Settings -> Define Partner Functions
Maintain Similar entries as mentioned below.
Function Function Type Usage Description Abbreviation
00000016 0013 B2B Requester RQ
00000017 0007 B2B Contact Person CP
00000018 0011 B2B Bidder BI
00000019 0012 B2B Vendor VD
00000020 0002 B2B Goods Recipient GR
00000025 0014 B2B Portal Provider PP
00000026 0008 B2B Responsible Employee RE
00000027 0017 B2B Ship-To Address DP
00000028 0003 B2B Invoice Recipient IR
00000029 0015 B2B Invoicing Party IP
00000030 0018 B2B Ship-From Address SP
00000034 0002 B2B Plant PLNT
00000038 0001 B2B Sold-to Party ORDR
00000039 0026 B2B Preferred Vendor PRVD
00000051 0019 B2B Purch. Org. Auth. For Release AREL
00000074 0025 B2B Service Agent SERV
00000075 0031 B2B Location LOCA
00000097 0034 B2B Invoicing Party Employee IPEm
Hope this will definitely help.
More details ->
For 1), see these links below ->
Partner function missing in backend PO
Re: Error in transmission while PO cration
"Multiple" partner data at PO header
Partner functions in plan driven MM-SUS
Re: Partner function not found
Number range for business partner
Re: Problem with BP. Assignment: Business partner person to user not unique
Error in creation of Employee for Business Partner
Re: enter exactly one partner of type vendor
Re: Business partner as Vendor and Invoicing Party
Partner functions in EBP for extended Classic Scenario
Classic Scenario PO has multiple OA Partner Functions for Vendor
For 2), see the pointers ->
There is an article written by Jason Didday at www.saptips.com entitled "mySAP SRM and SAP R/3 Partner Functions: Supporting OAs, VNs and IPs" that you may find useful.
In SRM, there is no standard relation betwwen plant and vendor master data.
You can use BBP_GET_VMDATA_CF BADI to add backend data in SRM while using BBPGETVD and BBPUPDVD transactions.
Replication of Ordering Address from R/3 to SRM
Re: Adding Partner Function to R/3 PO from SRM in Classic using BADI
Partner function Payee in SRM
Adding Partner Function to R/3 PO from SRM in Classic using BADI
Do let me know.
Regards
- Atul

Address Title for Vendor Replication

Similar Messages

Maybe you are looking for