Dun & Bradstreet SHADY

Any company that is going to call me like telemarketing and try to sell me things:"We just wanted to see about completing your background check and taking your D&B credit out of pending unverified status and make you a complete registered legal business!"me- you are welcome to do that but I will not pay for it.D&B "You don't want to have your credit profile with the business complete?me "My business credit is reported in more than 1 place than D&B and if someone is interested in checking my business documents they can go to the state website for free they don't need D&B reports to tell them I'm a registered business and I certainly don't need to spend the money for you to tell me I am a registered business... further more Equifax and Experian have a business credit report for my company that is available and more widely used for the type of credit I apply for and it's FREE!D&B "okay then I'll mark your file that you don't want to complete it and we will continue to send out the incomplete information" Makes me want to reach through the phone and... I feel like im talking to a collection agency not a company that is for me! they are like BBB, full of fraud.

Guess what TravellingNomad.ironically I was trying to log on to DnB this morning Locked out .i tried to check my company through check or company your or checking Other Company locked Out , 2 hours later received an Email.
Hello from Dun & Bradstreet,
We noticed you recently had difficulty accessing your dashboard, or were unable to complete your purchase.
It is our goal to ensure you have the best experience possible on our site. If you were unable to complete your purchase, perhaps a 10% Off Discount may peak your interest.
https://www.upsellit.com/hound/follow.jsp?s=dh_hTTN1437992716124&l=1&a=1 and use Promo Code: COMEBACK at checkout to save 10%!
If you did in fact experience trouble accessing your account, or if you would like to speak with a Certified Credit Advisor, you can reach us at (877) 562-3244.
Thank you,
Dun & Bradstreet Credibility Corp.
Hmmmmm
Could this because I requested a dispute the 4th time and when I got a email to log in to see the report and asked security I had no idea these questions . Now that's Shaddy !!

Similar Messages

What is Dun-Bradstreet Business Content? What is Nielson?

Hello Masters,
What is Dun-Bradstreet Business Content? What is Nielson?
I am bound to give points
Thanks and Best wishes,
I-BI

Hi,
those content are industry figures and statistic which s company can buy to Dun&Bradstreet or Nielsen.
SAP BW is providing preconfigured business content for this data.
One company could buy data and measure its results with its competitors.
Hope this helps...
Olivier.

Dun & Bradstreet credit management functionality

Hello experts,
My client wants to use Dun & Bradstreet credit management functionality, we are currently on SAP version 4.7 highest support pack SAP_APPL SAPKH47025.
How can I find out more about this product?
How much does it cost?
Where in SAP service marketplace should I request this?
How to go about implementing?
etc
Kind regards Steve D

Dun & Bradstreet, D&B as they are known are a credit agency.
They rate Companies. They review the Company Accounts, turnover, way the pay and produce credit limit recommendations.
You would need to contac them as to their cost.
How can you use them in SAP?
Well you can have an online facility where you down load their data and upload it to credit masters, FD32. Normally here you will need their DUNS number linked to a credit master and it will update the credit score and potentially the risk category.
As you have 4.7, you could chose to go with FSCM and the Credit Management processes that offers. it has a different link into D&B but you need to work out if the scoring you use for C/L creation, approval and change is just from D&B or internal rules are used as well.
lastly you need to consider if you will apply to the D&B on an adhoc basis, customer by Customer which is cheaper than them feeding you the data everytime they change their ratings.
please award points if useful.

Does Siebel and Dun & Bradstreet Integration Still Exist?

Hi All,
I'm wondering if Siebel partnership with Dun and Bradstreet still exist. There is very little or non existence of such integration and reference which I am able to find on Oracle web as well as Google. Firstly, I'm wondering of this partnership still. Secondly, if there is still such integration, can anyone provide further detail if what is available in Siebel for this integration? Thirdly, the customer reference. Also,one important area I'm interested to know is how the UI of this integration looks like in Siebel.
Thanks.

Derek,
Thank you for posting your question. D&B does have a direct integration into Siebel with a product named D&B360. For more detail please contact me at [email protected] or 512-380-4814 and I can assist you further.
Jim

Duns & Bradstreet Implementation for Vendor Analytics

Hi All,
Our client wants to go for D&B implemantation. We have provided the Vendor Master details extract to D&B and they have responded with the files (CSV) that needs to be uploaded to BI for Vendor Analytics.
We have not yet installed D&B BI content objects yet (DUNS number InfoObject and 0Vendor needs to be activated). As we have to reactivate 0Vendor and we already have some customization on the same (0Vendor_attr datasource has been enhanced), what all precautions need to be taken.
If someone has installed the D&B, any inputs/suggesstions will be really helpful. Thanks.
Regards,
Kavitha

Have you tried running the sql against your source? I ran this against one of our EBS instances and it runs fine.
If it runs OK I would next check what connection the Informatica workflow is using. Check the full session and workflow logs to make sure its connecting to the correct database.

Using D&B Data (Dun & Bradstreet)

Hi,
D&B delivers company data as offline databases. It is not clear to me if Data Services is able to read the D&B ofline databases using one of the default interfaces. Has anyone used D&B data within Data Integrator/ Data Services? What interface is needed to read D&B data from its online database?
thx
Helmut

Stephan,
Check [this page on saphelp|http://help.sap.com/saphelp_erp2005vp/helpdata/en/46/8ba60b504048a5be21d1e202030700/frameset.htm].
Kind regards,
Koen

Where to Store D&B # (DUNS) on customer master record

Hello,
I've been trying to find a field to store the Dun & Bradstreet (9 character DUNS #). I had heard there was a field available in R/3, but can't find it anywhere so I might have heard incorrectly. After doing some searches I can only find the field available on the BW system. I also came across a field on the vendor record but that's not going to be helpful either.
Is there a field to store a DUNS number on the customer master record? I'm on ECC6.
Thanks,
Jonathan

Hi jonathan
If you want to know where the data is getting is stored like customer changes (i.e. address changes, sold to another company, credit scores, etc...).Then go to sales area data ->environment->sales data and click on execute. System will show the tables and fields which have been changed and when they have been changed
use t.code VC/2 for sales summary , may be this will help you
Regards
Srinath

Adding new Field in Business Partner General Data

Hi All,
I'm working on a mySAP CRM 4.0 implementation.
I would like to extend the business partner data with this new three field:
1) Capital Stock
2) Base Number
3) Sales pl.
The three field are Dun & BradStreet information.
I created a BSP that show all Business Partner General Data and now we want to show also those fields.
In order to extend the BP data we received two suggestion:
The first one is to use the BP marketing Attributes.
The second is to use the Easy Enhancement Workbench.
I know that advantages of the EEW is the automatic creation of the layout (BSP & DYNPRO).
Doo you have any suggestion??
It's a good solution to use the EEW??
Thanks a lot.
Eugenio

Hi,
First of all thanks a lot for the fast reply.
I have to add some information:
The end-user will use the application only in PC-UI mode (through Enterprise Portal).
We are customizing the BSP application (Accounts).
I know that in past some colleagues used the EEW to extend or to add some field to application BP. I remember that the field (after Enhancement the new fields was visible in SAPGUI mode and in BSP mode).
Now my questions are the following:
1) Are you sure that I can use EEW only 10 times??
2) We are using the BAPI (CRMXIF_PARTNER_SAVE) in order to add Business Partner in the system; after the creation of the new fields with EEW the BAPI (CRMXIF_PARTNER_SAVE) will be able to insert the new fields?? Or we need to extend this BAPI with new fields?
The second question is very important for us because we have to import in the system about 30.000.000 of Business Partners.
Kind Regards.
Eugenio.

Need information about some queries

Hello, I need help in finding the documentation (use, rows, columns, free characteristics etc) about these queries. I've already looked in the BI documentation in help.sap.com but I haven't found anything about these ones. If anyone knows the links where I can find them or has info I would very much appreciate it.
Thank you!
Production capacity     ZPP_BW_Q02
Actual Activities - extended     0PP_C04_Q0004
Detailed Activity Analysis     0PP_C03_Q0019
Production Indicator     ZPP_C03
Delivery Perfomance     0PP_MP01_Q0003
PP Capacidades     ZPPCAPACITY
Repetitive manufacturing     ZPP_BW_Q03
Customer: Plan/Actual Sales     0SD_C01_Q030
Incoming Orders by Plant     0SD_C03_Q00004
Sales order material     0SD_C03_Q0012
Most Frequent Product Combination     0SD_C03_Q0020
Direct Business Volume per ADM     0SD_C03_Q0022
Decrease in Sales     0SD_C03_Q006
Sales Order and Sales Revenue Values by Sales Representative     0SD_C03_Q024
Preselection of Top Ten Customers     0SD_C03_Q025
Error-Free Order Processing - Top 10 Customers     0SD_C03_Q026
Amounts and Dates for Delivery Delay - Top 10 Customers     0SD_C04_Q0009
Amounts and Dates for Delivery Delay     0SD_C04_Q0010
Quotation Pipeline     0SD_C05_Q0007
Customer-Related Quotation Success (with Material)     0SD_C05_Q0008
Overview: Freight Documents and Invoices     0SD_MP02_Q0002
Plan Customer I     ZCUSTOMER3
Plan Customer II     ZCUSTOMER4
Analysis of Due Date for Net Payment (Business Partner)      0FIAR_C03_Q1005
Customers: Overview      0FIAR_C03_Q0007
Overdue Analysis (Business Partner)      0FIAR_C03_Q1004
List of Open Items for Due Date Analyses      0FIAR_O03_Q0001_CR
Asset List      0FIAA_C12_Q0001
Transaction Data Report      0FIAA_C11_Q0001
Depreciation Posted      0FIA_DS13_Q0001
Asset Acquisitions      0FIA_DS11_Q0001
Asset Retirements      0FIA_DS11_Q0004
Investments by Quarter      0FIA_DS11_Q0002
Transaction Data Report      0FIA_DS11_Q0003
Collection Agencies Receivables/Revenues      0FC_C03_Q0001
Monthly Overview of Installment Payments      0FC_C04_Q0001
Completed Installment Plans      0FC_C05_Q0001
Profit Center - Account View (SAP Analytics)      0PCA_MP01_Q0004
Profit Center - Balance Sheet (SAP Analytics)      0PCA_MP01_Q0002
Profit Center - Income Statement (SAP Analytics)      0PCA_MP01_Q0003
Profit Ctr Key Figure - Return on Investment (SAP Analytics)      0PCA_MP01_Q0001
Profit Center: Plan/actual/variance balance sheet accounts      0PCA_C01_Q0016

Throwing my hat in the ring for updates on this as well. I was searching for a good "Sales Orders by Sales Rep" query and couldn't find anything in the help.sap documentation. I did some where used queries on 0SALESEMPLY and came across all of these queries from just 0SD_C03 that aren't documented (as far as I can tell):
0SD_C03_DB_Q0001
D&B Revenue per Customer with family tree
0SD_C03_DB_Q0002
Dun & Bradstreet Duplicate Customers to one DUNS Number
0SD_C03_DB_Q0003
D&B Customer Revenue Analysis
0SD_C03_DB_Q0010
D&B Customer Details
0SD_C03_Q00004
Incoming Orders by Plant
0SD_C03_Q0001
Overview: Freight Documents and Invoices
0SD_C03_Q0012
Sales order material
0SD_C03_Q0015
Preselection Business Partner (only CRM)
0SD_C03_Q0016
Most Frequent Product Combination (only CRM)
0SD_C03_Q0017
Cross Selling Target Group
0SD_C03_Q0018
Sales Volume for Product Hierarchy
0SD_C03_Q0019
Sales Volume Decrease per Business Partner
0SD_C03_Q0020
Most Frequent Product Combination
0SD_C03_Q0021
Preselection Business Partner
0SD_C03_Q0022
Direct Business Volume per ADM
0SD_C03_Q0023
Sales Order and Sales Revenue Values from the Last 12 Months
0SD_C03_Q0024
Decrease in Sales
0SD_C03_Q0025
Incoming Orders of the Last 12 Months
0SD_C03_Q0026
Top 10 Materials Based on Incoming Orders of Last 12 Months
0SD_C03_Q0100
Returns per Business Partner
0SD_C03_Q0101
Sales Volume Development per Business Partner
0SD_C03_Q012
Returns per Customer Top N
0SD_C03_Q024
Sales Order and Sales Revenue Values by Sales Representative
0SD_C03_Q025
Preselection of Top Ten Customers
0SD_C03_Q026
Error-Free Order Processing - Top 10 Customers
0SD_C03_QDB001
Dun & Bradstreet Rationalization for All Customers

How to determine vendor minority indicator / status

We are using a manual process to update vendor minority indicator. Is there a service out there to automate the process? Is there a vendor (Dun Bradstreet) who can provide periodic updates based on vendor account number?
Any input is welcome.

hi ,
check table TBTCO.
YES. u can check for STATUS = P- Schedule/S---Released
regards
Prabhu
Edited by: Prabhu Peram on Sep 18, 2008 6:43 PM

System.log - need information about some errors

Hi there,
one of my customer has problems with fileserver volumes.
They unmount serveral times a day.
He is using 10.39 and 10.45, under 10.39 the problems occur.
It is currently not possible to migrate to 10.4.
Fileserver 1 is a Helios EtherShare 4th generation
Fileserver 2 is a W2K3-Server SP1, SFM installed
umounts occur on both servervolumes mounted on the desktop.
the system-log reports some errors, I can´t find a description on the internet... ;-(
So I hope you guys can help:
What does that mean?
"""AFP_VFS afpfs_Reconnect: Wrong version 4 or no more attempts 0"""
or that
AFP_VFS afpfs UserCommand: sosend failed for request 32 (sosend is a socket command)
Is there a request-reference-list?
What we actually did?
turn appletalk off, deactivated spanning tree on the switches, check for virusscanners on the windows server, used the maintenance-scripts, checked access-rights on the servervolumes, installed the actual updates for windows and helios ethershare servers...
Regards from germany...
PowerMac G5 Dual 2.3 Mac OS X (10.4.5)

Throwing my hat in the ring for updates on this as well. I was searching for a good "Sales Orders by Sales Rep" query and couldn't find anything in the help.sap documentation. I did some where used queries on 0SALESEMPLY and came across all of these queries from just 0SD_C03 that aren't documented (as far as I can tell):
0SD_C03_DB_Q0001
D&B Revenue per Customer with family tree
0SD_C03_DB_Q0002
Dun & Bradstreet Duplicate Customers to one DUNS Number
0SD_C03_DB_Q0003
D&B Customer Revenue Analysis
0SD_C03_DB_Q0010
D&B Customer Details
0SD_C03_Q00004
Incoming Orders by Plant
0SD_C03_Q0001
Overview: Freight Documents and Invoices
0SD_C03_Q0012
Sales order material
0SD_C03_Q0015
Preselection Business Partner (only CRM)
0SD_C03_Q0016
Most Frequent Product Combination (only CRM)
0SD_C03_Q0017
Cross Selling Target Group
0SD_C03_Q0018
Sales Volume for Product Hierarchy
0SD_C03_Q0019
Sales Volume Decrease per Business Partner
0SD_C03_Q0020
Most Frequent Product Combination
0SD_C03_Q0021
Preselection Business Partner
0SD_C03_Q0022
Direct Business Volume per ADM
0SD_C03_Q0023
Sales Order and Sales Revenue Values from the Last 12 Months
0SD_C03_Q0024
Decrease in Sales
0SD_C03_Q0025
Incoming Orders of the Last 12 Months
0SD_C03_Q0026
Top 10 Materials Based on Incoming Orders of Last 12 Months
0SD_C03_Q0100
Returns per Business Partner
0SD_C03_Q0101
Sales Volume Development per Business Partner
0SD_C03_Q012
Returns per Customer Top N
0SD_C03_Q024
Sales Order and Sales Revenue Values by Sales Representative
0SD_C03_Q025
Preselection of Top Ten Customers
0SD_C03_Q026
Error-Free Order Processing - Top 10 Customers
0SD_C03_QDB001
Dun & Bradstreet Rationalization for All Customers

IDOC - segment Qualifier

Dear all,
Do you know the transaction or an document which give the link between the Qualifier segment of an segment IDOC and the SAP field ?
for example : IDOC ORDERS05
segment E1EDK03
qualifier 002 : wished delivery date in VA01
segment E1EDK02
qualifier 050 : Delivery Order in segment description but correspond to PO number in VA01
I search to fill in the field PO Date but I don't find the qualifer segment.
Could you please help me ?
thanks
Véronique

Hi friends,
i thing your problem will solve.
E1EDK01 : IDoc: Document header general data
Segment definition E2EDK01005 Released since Release 45B , Segment length: 0357
ACTION : Action code for the whole EDI message
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 003, Offset : 0067. external length : 000003
HWAER : EDI local currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 004, Offset : 0070. external length : 000003
WKURS : Exchange rate
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 005, Offset : 0073. external length : 000012
ZTERM : Terms of payment key
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 006, Offset : 0085. external length : 000017
KUNDEUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 007, Offset : 0102. external length : 000020
EIGENUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 008, Offset : 0122. external length : 000020
BSART : Document type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 009, Offset : 0142. external length : 000004
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0146. external length : 000035
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 011, Offset : 0181. external length : 000018
BRGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0199. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 013, Offset : 0217. external length : 000003
FKART_RL : Invoice list type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 014, Offset : 0220. external length : 000004
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 015, Offset : 0224. external length : 000025
BSTZD : Purchase order number supplement
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 016, Offset : 0249. external length : 000004
VSART : Shipping Conditions
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 017, Offset : 0253. external length : 000002
VSART_BEZ : Description of the Shipping Type
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 018, Offset : 0255. external length : 000020
RECIPNT_NO : Number of recipient (for control via the ALE model)
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 019, Offset : 0275. external length : 000010
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 020, Offset : 0285. external length : 000001
AUTLF : Complete delivery defined for each sales order?
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 021, Offset : 0286. external length : 000001
AUGRU : Order reason (reason for the business transaction)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0287. external length : 000003
AUGRU_BEZ : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 023, Offset : 0290. external length : 000040
ABRVW : Usage Indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 024, Offset : 0330. external length : 000003
ABRVW_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 025, Offset : 0333. external length : 000020
FKTYP : Billing category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 026, Offset : 0353. external length : 000001
LIFSK : Delivery block (document header)
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 027, Offset : 0354. external length : 000002
LIFSK_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 028, Offset : 0356. external length : 000020
EMPST : Receiving point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 029, Offset : 0376. external length : 000025
ABTNR : Department number
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 030, Offset : 0401. external length : 000004
DELCO : Agreed delivery time
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 031, Offset : 0405. external length : 000003
WKURS_M : Indirectly quoted exchange rate in an IDoc segment
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 032, Offset : 0408. external length : 000012
E1EDK14 : IDoc: Document Header Organizational Data
Segment definition E2EDK14 Released since Release 30A , Segment length: 0038
QUALF : IDOC qualifer organization
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
ORGID : IDOC organization
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
E1EDK03 : IDoc: Document header date segment
Segment definition E2EDK03 Released since Release 30A , Segment length: 0017
IDDAT : Qualifier for IDOC date segment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0074. external length : 000006
E1EDK04 : IDoc: Document header taxes
Segment definition E2EDK04001 Released since Release 40B , Segment length: 0107
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 001, Offset : 0063. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0070. external length : 000017
MWSBT : Value added tax amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 003, Offset : 0087. external length : 000018
TXJCD : Tax Jurisdiction
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 004, Offset : 0105. external length : 000015
KTEXT : Text Field
internal data type : CHAR
Internal length : 000050 characters
Position in segment : 005, Offset : 0120. external length : 000050
E1EDK05 : IDoc: Document header conditions
Segment definition E2EDK05001 Released since Release 40A , Segment length: 0185
ALCKZ : Surcharge or discount indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KSCHL : Condition type (coded)
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 002, Offset : 0066. external length : 000004
KOTXT : Condition text
internal data type : CHAR
Internal length : 000080 characters
Position in segment : 003, Offset : 0070. external length : 000080
BETRG : Fixed surcharge/discount on total gross
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 004, Offset : 0150. external length : 000018
KPERC : Condition percentage rate
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 005, Offset : 0168. external length : 000008
KRATE : Condition record per unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 006, Offset : 0176. external length : 000015
UPRBS : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 007, Offset : 0191. external length : 000009
MEAUN : Unit of measurement
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0200. external length : 000003
KOBTR : IDoc condition end amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 009, Offset : 0203. external length : 000018
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 010, Offset : 0221. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 011, Offset : 0228. external length : 000017
KOEIN : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 012, Offset : 0245. external length : 000003
E1EDKA1 : IDoc: Document Header Partner Information
Segment definition E2EDKA1003 Released since Release 45A , Segment length: 0995
PARVW : Partner function (e.g. sold-to party, ship-to party, ...)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
PARTN : Partner number
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0066. external length : 000017
LIFNR : Vendor number at customer location
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 003, Offset : 0083. external length : 000017
NAME1 : Name 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 004, Offset : 0100. external length : 000035
NAME2 : Name 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 005, Offset : 0135. external length : 000035
NAME3 : Name 3
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 006, Offset : 0170. external length : 000035
NAME4 : Name 4
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 007, Offset : 0205. external length : 000035
STRAS : Street and house number 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 008, Offset : 0240. external length : 000035
STRS2 : Street and house number 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 009, Offset : 0275. external length : 000035
PFACH : PO Box
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0310. external length : 000035
ORT01 : City
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 011, Offset : 0345. external length : 000035
COUNC : County code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 012, Offset : 0380. external length : 000009
PSTLZ : Postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 013, Offset : 0389. external length : 000009
PSTL2 : P.O. Box postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 014, Offset : 0398. external length : 000009
LAND1 : Country Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 015, Offset : 0407. external length : 000003
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 016, Offset : 0410. external length : 000035
PERNR : Contact person's personnel number
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 017, Offset : 0445. external length : 000030
PARNR : Contact person's number (not personnel number)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 018, Offset : 0475. external length : 000030
TELF1 : 1st telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 019, Offset : 0505. external length : 000025
TELF2 : 2nd telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 020, Offset : 0530. external length : 000025
TELBX : Telebox number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 021, Offset : 0555. external length : 000025
TELFX : Fax number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 022, Offset : 0580. external length : 000025
TELTX : Teletex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 023, Offset : 0605. external length : 000025
TELX1 : Telex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 024, Offset : 0630. external length : 000025
SPRAS : Language key
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 025, Offset : 0655. external length : 000001
ANRED : Form of Address
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 026, Offset : 0656. external length : 000015
ORT02 : District
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 027, Offset : 0671. external length : 000035
HAUSN : House number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 028, Offset : 0706. external length : 000006
STOCK : Floor
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 029, Offset : 0712. external length : 000006
REGIO : Region
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 030, Offset : 0718. external length : 000003
PARGE : Partner's gender
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 031, Offset : 0721. external length : 000001
ISOAL : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 032, Offset : 0722. external length : 000002
ISONU : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 033, Offset : 0724. external length : 000002
FCODE : Company key (France)
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 034, Offset : 0726. external length : 000020
IHREZ : Your reference (Partner)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 035, Offset : 0746. external length : 000030
BNAME : IDoc user name
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 036, Offset : 0776. external length : 000035
PAORG : IDOC organization code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 037, Offset : 0811. external length : 000030
ORGTX : IDoc organization code text
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 038, Offset : 0841. external length : 000035
PAGRU : IDoc group code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 039, Offset : 0876. external length : 000030
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
ILNNR : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 041, Offset : 0936. external length : 000070
PFORT : PO Box city
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 042, Offset : 1006. external length : 000035
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 043, Offset : 1041. external length : 000002
TITLE : Title
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 044, Offset : 1043. external length : 000015
E1EDKA3 : IDoc: Document Header Partner Information Additional Data
Segment definition E2EDKA3 Released since Release 30D , Segment length: 0073
QUALP : IDOC Partner identification (e.g.Dun&Bradstreet number)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
STDPN : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 002, Offset : 0066. external length : 000070
E1EDK02 : IDoc: Document header reference data
Segment definition E2EDK02 Released since Release 30A , Segment length: 0058
QUALF : IDOC qualifier reference document
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
POSNR : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0101. external length : 000006
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0107. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 005, Offset : 0115. external length : 000006
E1EDK17 : IDoc: Document Header Terms of Delivery
Segment definition E2EDK17 Released since Release 30A , Segment length: 0076
QUALF : IDOC qualifier: Terms of delivery
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
LKOND : IDOC delivery condition code
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0066. external length : 000003
LKTEXT : IDOC delivery condition text
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 003, Offset : 0069. external length : 000070
E1EDK18 : IDoc: Document Header Terms of Payment
Segment definition E2EDK18 Released since Release 30A , Segment length: 0089
QUALF : IDOC qualifier: Terms of payment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
TAGE : IDOC Number of days
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
PRZNT : IDOC percentage for terms of payment
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 003, Offset : 0074. external length : 000008
ZTERM_TXT : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 004, Offset : 0082. external length : 000070
E1EDK35 : IDoc: Document Header Additional Data
Segment definition E2EDK35000 Released since Release 45A , Segment length: 0078
QUALZ : Qualifier for IDoc additional data
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
CUSADD : Data Element Type CHAR Length 35
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
CUSADD_BEZ : Character field of length 40
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0101. external length : 000040
E1EDK36 : IDOC: Doc.header payment cards
Segment definition E2EDK36000 Released since Release 45A , Segment length: 0114
CCINS : Payment cards: Card type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
CCINS_BEZEI : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 002, Offset : 0067. external length : 000020
CCNUM : Payment cards: Card number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 003, Offset : 0087. external length : 000025
EXDATBI : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0112. external length : 000008
CCNAME : Payment cards: Name of cardholder
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 005, Offset : 0120. external length : 000040
FAKWR : Maximum amount
internal data type : CURR
Internal length : 000015 characters
000002 decimal places, without sign
Position in segment : 006, Offset : 0160. external length : 000017
E1EDKT1 : IDoc: Document Header Text Identification
Segment definition E2EDKT1002 Released since Release 45A , Segment length: 0089
TDID : Text ID
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
TSSPRAS : Language Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0067. external length : 000003
TSSPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 003, Offset : 0070. external length : 000002
TDOBJECT : Texts: Application Object
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 004, Offset : 0072. external length : 000010
TDOBNAME : Name
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 005, Offset : 0082. external length : 000070
E1EDKT2 : IDoc: Document Header Texts
Segment definition E2EDKT2001 Released since Release 40A , Segment length: 0072
TDLINE : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 001, Offset : 0063. external length : 000070
TDFORMAT : Tag column
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 002, Offset : 0133. external length : 000002
E1EDP01 : IDoc: Document Item General Data
Segment definition E2EDP01007 Released since Release 640 , Segment length: 0542
POSEX : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 001, Offset : 0063. external length : 000006
ACTION : Action code for the item
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0069. external length : 000003
PSTYP : Item Category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 003, Offset : 0072. external length : 000001
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 004, Offset : 0073. external length : 000001
MENGE : Quantity
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 005, Offset : 0074. external length : 000015
MENEE : Unit of measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 006, Offset : 0089. external length : 000003
BMNG2 : Quantity in price unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 007, Offset : 0092. external length : 000015
PMENE : Price Unit of Measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0107. external length : 000003
ABFTZ : Agreed cumulative quantity
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 009, Offset : 0110. external length : 000007
VPREI : Price (net)
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 010, Offset : 0117. external length : 000015
PEINH : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 011, Offset : 0132. external length : 000009
NETWR : Item value (net)
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0141. external length : 000018
ANETW : Absolute net value of item
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 013, Offset : 0159. external length : 000018
SKFBP : Amount qualifying for cash discount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 014, Offset : 0177. external length : 000018
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 015, Offset : 0195. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 016, Offset : 0213. external length : 000003
EINKZ : Flag: More than one schedule line for the item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 017, Offset : 0216. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 018, Offset : 0217. external length : 000003
PREIS : Gross price
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 019, Offset : 0220. external length : 000018
MATKL : IDOC material class
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 020, Offset : 0238. external length : 000009
UEPOS : Higher-Level Item in BOM Structures
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 021, Offset : 0247. external length : 000006
GRKOR : Delivery group (items delivered together)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0253. external length : 000003
EVERS : Shipping instructions
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 023, Offset : 0256. external length : 000007
BPUMN : Denominator for Conv. of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 024, Offset : 0263. external length : 000006
BPUMZ : Numerator for Conversion of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 025, Offset : 0269. external length : 000006
ABGRU : Reason for rejection of quotations and sales orders
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 026, Offset : 0275. external length : 000002
ABGRT : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 027, Offset : 0277. external length : 000040
ANTLF : Maximum number of partial deliveries allowed per item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 028, Offset : 0317. external length : 000001
FIXMG : Delivery date and quantity fixed
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 029, Offset : 0318. external length : 000001
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 030, Offset : 0319. external length : 000001
BRGEW : Total weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 031, Offset : 0320. external length : 000018

BI content - Error on activate 0DB IOBJ

Hello,
I'd try to activate IOBJ in BC, but all of them that need 0DB (Dun & Bradstreet) has problems in activation like that (like a sample of errors).
I opened an incident to SAP Support, but unitl now I don't have any answer.
Object '0DB87SIC1' (IOBJ) of type 'InfoObject' is not available in version 'D'
Object '0DBADDRES1' (IOBJ) of type 'InfoObject' is not available in version 'D'
Object '0DBADDRES2' (IOBJ) of type 'InfoObject' is not available in version 'D'
Object '0DBANSALES' (IOBJ) of type 'InfoObject' is not available in version 'D'
Object '0DBANSLUS' (IOBJ) of type 'InfoObject' is not available in version 'D'
Object '0DBAREACOD' (IOBJ) of type 'InfoObject' is not available in version 'D'
Object '0DBBUSNAME' (IOBJ) of type 'InfoObject' is not available in version 'D'
Object '0DBCEONAME' (IOBJ) of type 'InfoObject' is not available in version 'D'
Details of error:
Object '0DB87SIC1' (IOBJ) of type 'InfoObject' is not available in version 'D'
Message No. RSO252
Diagnosis
You wanted to generate an object with the name '0DB87SIC1' (in transport request IOBJ) of type 'InfoObject' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version D. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System Response
The object was not taken into account in the next stage of processing.
SC versions:
SAP_BASIS     740     0009
SAP_ABA             740     0009
SAP_GWFND     740     0009
SAP_UI             740     0010
PI_BASIS             740     0009
ST-PI             740     0001
BI_CONT             757     0005
BI_CONT_XT     757     0005
SAP_BW             740     0009
GRCPINW             V1100_7310008
CPMBPC             810        0004
POASBC             100_731     0006
HANABPC        810             0004
ST-A/PI          01R_731     0000

Okay, sorry I think I jumped right in without knowledge of version. So I think you will have to reinstall the business content and before that you will have to activate the business function in SFW5.
You do this in transaction SFW5, open the folder Enterprise Business Functions.
For the Business Function DUN_BRADSTREET_CONTENT turn the Flag Planned Status (Business Function will be activated)on.
Activate your setting by clicking on the button Activate Changes.
Also refer SAP Note: 425632 - BW Content for Dun & Bradstreet which talks about activating the busness function before installation of business content for D&B. This SAP note is for BW 7.4.
Hope this helps.
Regards
Amit

Form submits

I have following jsp page in struts. if you see, this page has four editable textfields and one submit button. when i edit four textfiled values and then try to press submit, I want to submit these four textfiled values to a stored procedure which updates the fields in database and then re-display this same jsp page, with those textfield values re-displayed. I do have a Form class which has get/set methods for these textfield values. i also have a Action class. I want to know how this whole submit thing works. which code gets invoked when.
problem: No values get submitted after submit button is pressed.
Same jsp page is not redisplayed.
<%@ page language="java" %>
<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
<%@ taglib uri="/WEB-INF/struts-form.tld" prefix="form" %>
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
<%@ taglib uri="http://jakarta.apache.org/taglibs/log-1.0" prefix="log" %>
<%@ page import="com.mmm.is.PSS.pim.data.*" %>
<html:html locale="true">
<head>
<link rel="stylesheet" href="../swa/c/cdc.css" type="text/css">
<link rel="stylesheet" href="../swa/c/apps.css" type="text/css">
</head>
<body>
<html:errors/>
<html:form action="/company.do">
<html:hidden property="update" value="false"/>
        <table border="0" cellspacing="0" cellpadding="0" width="100%" class="content">
          <tr bgcolor="#ffffff" valign="top" align="left" >
            <td colspan="2" ><span class="contenttitlealt"><bean:message key="PIMBeGeoinfo.businessinfo" /></span></td>
          </tr>
          <tr bgcolor="#ffffff" valign="top" align="left" >
            <td width="26%" ><bean:message key="PIMBeGeoinfo.partnername"/><br>
              (Legal Name)</td>
            <td width="74%"> <bean:write name="PIMBeGeoForm" property="partnerName" /></td>
          </tr>
          <tr bgcolor="#ffffff" valign="top" align="left" >
            <td width="26%" ><bean:message key="PIMBeGeoinfo.countrygroup"/></td>
            <td width="74%"><bean:write name="PIMBeGeoForm" property="partnerCountry" /></td>
          </tr>
          <tr bgcolor="#ffffff" valign="top" align="left" >
            <td width="26%" ><bean:message key="PIMBeGeoinfo.webaddress"/></td>
            <td width="74%">
              <input type="text" class="inputtext" value=<bean:write name="PIMBeGeoForm" property="partnerURL"/> >
            </td>
          </tr>
          <tr bgcolor="#ffffff" valign="top" align="left" >
            <td width="26%" ><bean:message key="PIMBeGeoinfo.emaildomain"/></td>
            <td width="74%">
              <input type="text" class="inputtext" value=<bean:write name="PIMBeGeoForm" property="partnerEmailDomain" /> >
            </td>
          </tr>
          <tr bgcolor="#ffffff" valign="top" align="left" >
            <td width="26%" ><bean:message key="PIMBeGeoinfo.dunsnumber"/></td>
            <td width="74%">
              <input type="text" class="inputtext" size="15" value=<bean:write name="PIMBeGeoForm" property="partnerDUNSNumber" /> >
              <a class="contentlink" href="https://www.dnb.com">Request a DUNS
              Number</a> from Dun & Bradstreet. </td>
          </tr>
          <tr bgcolor="#ffffff" valign="top" align="left" >
            <td width="26%" ><bean:message key="PIMBeGeoinfo.description"/></td>
            <td width="74%">
              <textarea class="inputtext" style="width:100%;" rows="4"><bean:write name="PIMBeGeoForm" property="partnerDescription"/> </textarea>
            </td>
          </tr>
          <tr bgcolor="#ffffff" valign="top" align="left" >
            <td width="26%" > </td>
            <td width="74%">
             <input type="button"   value=<bean:message key="PIMBeGeoinfo.button" /> >
            </td>
          </tr>
        </table>
      <table border="0" cellpadding="0" cellspacing="0" width="100%">
        <tr>
          <td class="content" height="2"><img src="../swa/i/s.gif" width="1" height="3" alt=""></td>
        </tr>
        <tr>
          <td bgcolor="#cccccc" class="content"><img src="../swa/i/s.gif" width="1" height="3" alt=""></td>
        </tr>
      </table>
               <span class="contenttitlealt">Important Information</span>
          <br>
          <br>
          <span class="content">
        <table border="0" cellpadding="0" cellspacing="0" width="100%" class="appstablecolor">
          <tr>
            <td width="6"><img src="../swa/i/s.gif" width="6" height="26" alt=""></td>
            <td width="100%" nowrap><img src="../swa/i/s.gif" width="1" height="5" alt=""><br>
              <span class="moduletitlerev">Other Details</span> <br>
              <img src="../../images/spacer.gif" width="1" height="5" alt=""></td>
            <td width="7" align=head
            "right" valign="top"><img src="../swa/i/corner_ur_7.gif" width="7" height="7" alt=""></td>
          </tr>
        </table>
        
        <table border="0" cellpadding="0" cellspacing="0" class="appstablecolor" width="100%">
          <tr valign="top" align="left">
            <td width="100%" >
              <table border="0" cellspacing="1" cellpadding="3" width="100%" class="modulecontent">
                <tr valign="top" align="left">
                  <td width="40%" bgcolor="#ffffff" ><span class="modulesubhead"><bean:message key="PIMBeGeoinfo.hqaddress" /> </td></span></td>
                  <td width="20%" bgcolor="#ffffff"> <span class="modulesubhead"><bean:message key="PIMBeGeoinfo.countrygroup"/></span>
                  </td>
                  <td width="17%" bgcolor="#ffffff"><span class="modulesubhead"><bean:message key= "PIMBeGeoinfo.hqcam" /></span></td>
                  <td width="23%" bgcolor="#ffffff"><span class="modulesubhead"><bean:message key= "PIMBeGeoinfo.partneradmin" /></span></td>
                </tr>
                <logic:iterate id="site" name="PIMSite">
                <tr valign="top" align="left">
                  <td width="40%" bgcolor="#ffffff" >
                  <bean:write name="site" property="headQuarter"/><br>
                    <bean:write name="site" property="siteAddress1"/> <bean:write name="site" property="siteAddress1"/> <bean:write name="site" property="siteAddress1"/> <br>
                     <bean:write name="site" property="siteCity"/> <bean:write name="site" property="siteState"/>, <bean:write name="site" property="siteZipCode"/><br>
                    <bean:write name="site" property="sitePhone"/></td>
                  <td width="20%" bgcolor="#ffffff"> <bean:write name="site" property="siteCountry"/></td>
                  <td width="17%" bgcolor="#ffffff"><a href="mailto:[email protected]?subject=Email from mmm Partner Self Service" class="modulecontentboldlink"><bean:write name="site" property="channelAcctMgr"/></a></td>
                  <td rowspan="2" bgcolor="#ffffff" width="23%">Lisa Simpson<br>
                    Peter Parker
                  </td>
                </tr>
                </logic:iterate>
              </table>
            </td>
          </tr>
        </table>
          </span>
</html:form>
</body>
</html:html>

You didn't assign a name attribute your input field (< input type="text" name="myField" ...> ! The fields are submitted as request parameters in the form {$name}={$value}.
It might help to read about ActionForms and replace the whole input html tags with html:text tags from struts.
I'd recommend the articles on:
http://www.fawcette.com/javapro/2002_10/online/servletsjsp_bkurniawan_10_28_02/
http://www.fawcette.com/javapro/2003_01/online/servletsjsp_bkurniawan_01_28_03/
(Both are articles in a series don't forget to look at the other parts, too)
Yours,
Stefan

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
<u>Which SRM and R/3 versions are you using ?</u>
<b>Please go through the following SAP OSS Notes, which will help -></b>
<u>Note 738777 Problems with form of address text during transfer from UME
Note 674481 BBPGETVD/BBPUPDVD: Problems with form of address texts</u>
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

Dun & Bradstreet SHADY

Similar Messages

Maybe you are looking for