UDT & UDF for Vendor's Address

Hi Experts,
A client has a requirement of defining Transporter's name and address on marketing documents and ultimately printing them on the Sales Order,Delivery and A/r invoices.
The requirement is that the transporter (defined as Vendor) should appear on the logistics tab of the Sales Order Document and it could be selected as lookup from the master's data.
Can this be done by using a user defined field and table. The version being used is 2007A PL42.
Please advise ..
Regards,
Asap

Hello ASAP..I would rather prefer to address you by name if you could sign your name in your future threads...
Displaying anything other than whats is available in the logistics tab of the Sales marketing document would need fields to be made available on this tab and this would need SDK coding and customization.
Defining UDF's is a good option but they would not appear on the logistics tab. As far as fetching the information from the Vendor Master is quite achievable...and can be done using Formatted Searches
Suda

Similar Messages

CDHDR does not capture the Tcode for vendor master address changes:

Hi Guys,
Wish you a happy new year.
I have the problem to track the changes of the vendor master. I have a vendor master, which got changed by one user. If I look the change history, I can be able to see the change document number, old value and new value. based on that I used CDHDR table to find out the TCODE which is used for this change, but found no value in the TCODE field. What is the meaning of this? Is it meant to say that this field is updated by other sources other than direct changes (XK02/MK02)? If such a case, is it possible to find out the program or LSMW or BW, etc...which is used for this change?

>
Smart Sometimes wrote:
> do we have the option to search the changes based on the USER id for a particular date?
Which userid? SCN or SAP userid?

Idoc serialization for vendor and address master

Hi friends,
My gole is to transfer vendor master data from one sap ecc system to other ecc through PI.
I have achived this but the gmail and address data is not transfering as this is not a part of vendor master but even this address data need to passed to receiver system when ever there is change and creation of vendor.
Then i refered note Note 752194 - Serialization of IDoc processing and few threads in sdn ..
i am trying to do this serialization but i am facing issues to trigger idocs.
first this is the way we need to achive this.
if so adrmas is of type bapi so how can we group using Serialization Group of mesage type ..
guide me how to achive this.
And my vendor message type is customized one with zcremas_Xxx.
Regards
Vijay
Edited by: vijay Kumar on Dec 16, 2010 6:48 AM

Hi Vijay,
I am not sure whether you are active in SDN or not. I need your help in IDOC serialization
I have the same requirement like you here I need to Post ADRMAS and CREMAS. I am able to generate both the idocs succefully but the ADRNR is not assigned to the created Vendor. I might be missing something in config or in code.
Please reply to this thread and help me.

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....

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

Vendor Email Address(Urgent)

Hi,
Can some one help me regarding extracting the vendor email address.Email can be obtained from ADR6 but need to know the lifnr and personal number.How do I get a unique personal number for a vendor so that i can query ARD6 and get the mail address.
Thanks
Shyam

hi,
i am not saying that adrnr number is same as personnumber you misinterpreted me.
i was saying that for a particular adrnrnumber say 0000000145 , there exists various person number and these person number are in many cases same .
Address Number Person numb
0000000121
0000000145 0000001735
0000000145 0000002919
0000000145 0000002919
0000000145 0000004153
0000000145 0000004193
0000000145 0000004211
0000000145 0000004702
0000000145 0000005050
0000000145 0000005161
0000000145 0000005184
0000000145 0000005184
0000000145 0000005186
0000000145 0000005186
0000000145 0000005190
0000000145 0000005209
0000000145 0000009182
0000000145 0000010809
0000000145 0000017254
0000000145 0000017346

Agewise Outstanding Report for Vendors report

Hi All,
In SAP, Agewise Outstanding Report for Vendors report coming with Vendor Master Details along with Address details in the report S_ALR_87012085 - Vendor Payment History with OI Sorted List which is not really required. Hence we need to remove all un necessary details. We need only a signle line report for each vendor like below.
Vendor Code Vendor Name Due - 30 days Due - 60 days Due 90 Days Due 120 days and more than above
The selection of period option is already available in std SAP. We have to change the output report only. This is rquired for Audit purpose.
Please help me in the above issue.
Regards
Vinu

Hello,
The following example I have given is for customers.
The only difference is in transaction codes. For customer you go to FDI1, for vendor you go to FKI1 (reports).
For Customer you go to FDI4, for vendor you go to FKI4 for forms.
Remaining all are the same.
Hello,
Go to transaction code FDI4
Select Form Type RFFRRD20 Line item analysis
Give your form name and description
Structure (Two axis) - as defaulted
Click on Create
You will have lead column
Delete the rows 2, 3 and 4
Double click on column 1
Enter the customer numbers from 1 to 999999
First column double click (A)
Slelect following values
Due date analysis 1
Days for net due date 0 to 30
Give the short name, medium name and long text for the column.
Repeat this step in next columns like 31 to 60, 61 to 90, 91 to 120 and 121 to 99999 days etc in other columns and select due date analysis 1. (B,C,D,E)
Create one more column by way of formula. To create a new column you need to double click on blue line. Put formula add all five columns you have created above. (F = ABCDE)
You prepare one more column with
Due date analysis 2 (G)
Now you prepare one more column add (F+G) = This will be total open items = over due and not due.
Now go to FDI1 and prepare a report - assign the form created in FDI4 to the report.
Characteristics you need to select are
Account Type (Select Account Type as D for customers)
Currency
Customer
Document Type
Special G/L Ind
Company Code
Change the output types and options according to your requirement.
Refer FDI2 and FDI3 for other standard reports created.
Refer FDI5 and FDI6 for other standard forms created.
Save your report and execute.
Regards,
Ravi

How to get customer and vendor street addresses 4 and 5?

I need to know what table/field has the customer and vendor street addresses 4 and 5 stored in to them and how to access these fields.
This is for mapping on a LSMW customer and vendor data conversion.
Thanks!
Scortt

Thread should be moved to
Such fields do belong to address management tables. eg:ADRC-NAME3, ADRC-NAME4...
In other words they do not belong to customer master data so they are not reachable directly from customer master data fields.
The link is KNA1-ADRNR = ADRC-ADDRNUMBER
You might face difficulties in the mapping except if you plan to process in LSMW both DEBMAS idocs AND ADRMAS idocs
Alain

Slow performance creating UDT/UDF

When creating UDT/UDF via SAPbobsCOM.UserTableMD and SAPbobsCOM.UserFieldMD OR via SAPbobsCOM.Company.GetBusinessObjectFromXML(...) we experience extreme slow performance. One field of a table takes at least a second to be created.
We already checked the DB/Server, no problems there (in fact, it does not even show up as laggy.
Any hints? Is there so much data to be transported from client to server or what might be wrong?
Krischan

My setup takes between 8 and 15 seconds to create 65 user defined fields and one user defined table.
As I am able to watch the progress, I experience that creating user defined fields for documents is much slower than creating a user defined field for a user defined table.
Personally I think it's because every time a document udf is created, every document table is altered by mssql (the udfs are physically added to every table).
At least it don't take a whole second per table, which definitly sounds like "too much" to me...

Error message "No business partner could be created for vendor ..."

Dear experts,
I had made all the customizing settings for BP and CVI vendor/customer - BP integration and synchronization settings before. BP creation from vendor and usage within Real Estate was working with no problems. When i tried to create a new BP role recently i must have changed the settings and now when creating BP from vendor (FLBPC1) i get the following message:
No business partner could be created for vendor"
The long text of the message is:
Message no. CVIV_UI013
Diagnosis
No business partner could be created from the vendor selected.
System Response
An error occurred when creating a business partner from the vendor selected. This error prevents data from being transferred and saved. This could be due to the following:
Fields have been left blank in the vendor that are set as required entry fields for the business partner.
Settings for assigning Customizing values for the vendor to the business partner are incorrect.
Procedure
Start the Post Processing Office and check the error message. Make the necessary corrections.
I have checked all my customizing settings one by one but cant locate anything missing or wrong.
Also, in 956054 it is said that i must perform various migration reports, but i believe if it did work before without running these reports, this couldnt not be the problem now.
Any help would be appreciated
Thanks

Hi,
reason is the following.
The customer / vendor doesn't use special attribute to differentiate
between persons and organizations - in opposite to BP.
You can achieve what you want to do by using a BAdI prepared for that:
You'll find this in IMG transaction SPRO:
Cross-Application Components
Master Data Synchronization
    Customer/Vendor Integration
      Business Partner Settings
        BAdI: Data Assignment of Form of Address from Customer/Vendor t
Please read documentation of this BAdI in IMG.
You may use standard implementation CVI_MAP_BP_CATEGORY.
You also may create own implementation of the BAdI, if you want to
differentiate on other attributes.
Hope that helps.
Regards,
Franz

SAP MDM Vendor email addresses are not in order when sent to SAP R/3

Hi Experts,
We were trying to maintain vendor email addresses in this order in SAP MDM:
E-mail address: massupa@nexus
Sequence Number: 001
E-mail address: win@nexus
Sequence Number: 002
E-mail address: satita@nexus
Sequence Number: 003
But when saving the record, its order get mixed up like below: (I believe it was arranged alphabetically automatically---> is this the standard MDM functionality?!)
E-mail address: massupa@nexus
Sequence Number: 001
E-mail address: satita@nexus
Sequence Number: 003
E-mail address: win@nexus
Sequence Number: 002
When it gets syndicated to ECC, its order was maintained incorrectly with incorrect IDs:
E-mail address             ID
massupa@nexus        001
satita@nexus              002   -
> should be 003
win@nexus                 003 -
> should be 002
we checked both the XML Files and the IDOC and found that it has the same order maintained in SAP MDM
massupa@nexus        001
satita@nexus              003
win@nexus                 002
But how come the IDs were changed in R/3?
Many thanks in advance!

Hi Mike,
As per your requirement, i feel that for ID either you can create a new field say sequence ID in this e-mail addresses table of MDM and thus can syndicate it or can also use ID as key using remote key concept. I mean for this e-mail addresses table, you can set property Key mapping = yes in MDM Console and thus can use this IDs as key for this email address e.g. for massupa@nexus you can save ID as Key.
So during syndication, map this field with target IDOC structure field and I mean Remote Key under e-mail addresses table with IDOC ID target field. In this way you can have correct IDs with their corresponding email addresses.
Kindly let me know if you are looking for something else.
Regards,
Mandeep Saini

Solved - Group Fields for Vendor Master Records in IMG

This was the solution.
The new field's data element I added to LFB1 did not have the "change document" field checked. I made that change and now that field shows up in IMG.
Hello all,
I added an append structure to the table LFB1. This structure has 1 field. I then created a "Modification-Free Enhancement of Vendor Master Record" to add the new LFB1 field to the vendor master screen, edit and display screens. This is the 3rd time I have done this. So far so good.
Now our functional analyst went into IMG to add this new LFB1 field to a "Group Fields for Vendor Master Records" which we have done 2 other times.
The new LFB1 field does not show up in the list of possible Table-fields.
There must be some other step I am missing.
Does any of this ring a bell? We are on version 4.7.
Thanks
Bruce
p.s.
This is the IMG path for adding 'Field Groups' to vendor master fields.
Financial Accounting/
Accounts Receivable and Accounts Payable/
Vendor Accounts/
Master Data/
Preparations for Creating Vendor Master Data/
Group Fields for Vendor Master Records
Edited by: Bruce Tjosvold on Nov 21, 2008 1:18 PM

Hi Vandana,
There are several tables that are contain Vendor Master related data which can be used for extraction to BW. Some of the tables which can be useful for you are:
LFA1 : Vendor Master (General Section)
LFM1 : Vendor master record purchasing organization data
LFBW : Vendor master record (withholding tax types) X
WYT3 : Partner Functions
LFBK : Vendor Master (Bank Details)
LFB1: Vendor Master (Company Code)
ADRC: Addresses (Business Address Services)
ADR3: Fax Numbers (Business Address Services)
ADR6: SMTP Numbers (Business Address Services)
ADRT: Communication Data Text (Business Address Services)
You may use the Data sources mentioned in the previous update from Venky above namely :
0VENDOR_ATTR --- for master data attributes
0VENDOR_TEXTS -- For texts
Since the fields that you are using are from different tables so its better if you go for a Generic Data source where you can use the fields as per your requirement.
Thanks
Pawan
Edited by: pawan190187 on Aug 19, 2011 12:40 PM

Settign partner function for vendor

Hi..
I am trying to configure partner function for a vendor who has different oredring adress,
Can anyone explain me the stpes / details of how to configure a Partner function for vendor so that when i give the partner function in PO the adress of the partner function should be displayed.
And secondly if i create different partner function where do i maintain the address for each partner function.
Suggestions will be rewarded..
Regards

Hi,
check this thread
Partner function
thanks
suresh

How to add email option for vendor.

Hello all,
I looked for adding an email to the vendor in xk01, but there was no option of email field. I want to post FCEM output to test whther the output working fine thorugh email.
Plz advice.

Hi,
If you are using sap delivered vendor account group, system defualt shows email address in vendor master data.
In address tab, communication segment you can see the vendor email address.
Or Goto OMSG t.code choose vendor account group, double click on general data.
double click on communication, check the Internet mail address field and save.
Regards,
Chandra

UDT & UDF for Vendor's Address

Similar Messages

Maybe you are looking for