Sender FCC Details

Hi,
How to specify the sender fcc details for following structure
<header>
 <Record>
 <field1>
 <field2>

HI Guys,
How about the sender file is of such format
Header1,Item1 details
Header1,Item2 Details
Header2, Item1 Details
Header2,item2 Details
Header3, Item1 Details
I need to map this file format to IDOC strucutre, In Header there is a filed which is the Key value to identify the change in header.
Eg: Order Number is the field in the following file which identifies the change in header: First three fields are header details and following are the item details:
ABC,ON1,22,Item1,XX
ABC,ON1,33,Item2,FF
ABC,ON2,44,Item1,MM
ABC,ON3,66,Item1,LL
How would be the Data type strcuture to capture this type of falt file strcuture and FCC parameters?
I need to send a single IDOC per one header with multiple Items. is it possible to achieve?
Thanks
Rajeev

Similar Messages

Error in sender FCC

Hi,
I am facing an error in sender fcc its:
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 1 according to structure 'Pricebook_Data':java.lang.Exception: ERROR in configuration / structure 'Pricebook_Data.': More elements in file csv structure than field names specified!
My source structure is :
Pricebook_abc (root1)
            Pricebook_Data (root2)
                 field1
                 field2
and my sender fcc is:
Document name : Pricebook_abc
Document namespace: urn:xxxxxxx
Recordset name: pricebook
Recordset structure: Pricebook_Data,*
Recordsets per message: *
Pricebook_Data.fieldNames     field1,field2
Pricebook_Data.fieldSeparator     ,
Pricebook_Data.endSeparator     'nl'
ignoreRecordsetName     true
I am unable to rectify the error. Please help me.
Thanks & Regards,
Pragathi.
Edited by: Pragathi on Jan 15, 2010 1:40 PM
Edited by: Pragathi on Jan 15, 2010 1:41 PM
Edited by: Pragathi on Jan 15, 2010 1:41 PM

Hi,
The error was saying that.. the no of fields you are getting in the source are diff from that you have mentioned in FCC.
Can you just copy and paste the source csv file? and the exact XML structure?
Regards,
Swetha.

How to configure purchase requistion in third party sale pls send me detail

dear expert
how to configure purchase requistion in third party sale pls send me details. waiting your valuable reply
vicky

you can find the details in the below links
Re: THird party sales complete scenario
http://wiki.sdn.sap.com/wiki/display/ERPLO/PROCEDURETOCREATETHIRDPARTY+SALES
http://www.sap-img.com/sap-sd/process-flow-for-3rd-party-sales.htm
Regards

Hierarchical Structure in Sender FCC

Hi all,
I am working on a file to file scenario.
The sender data type is in following format -
File_Header
Record_ID
Filler_S
Batch_Header
Record_ID
Filler_S
Payment_Node
Record_ID
Filler_S
All the nodes are with key fields.
File_Header Keyfield - 1, Batch_Header Keyfield - 2, Payment_Node Keyfield - 3.
I want to know whether it is possible to have FCC on sender File adapter for this hierarchical structure.
The source XML message should be in following format -
<?xml version="1.0"; encoding="UTF-8"?>
<Test>
<File_Header>
<Record_ID>1</Record_ID>
<Filler_S>12</Filler_S>
</File_Header>
<Batch_Header>
<Record_ID>2</Record_ID>
<Filler_S>12</Filler_S>
<Payment_Record>
<Record_ID>3</Record_ID>
<Filler_S>12</Filler_S>
</Payment_Record>
</Batch_Header>
</Test>
Currently I am getting source XML in this format.
<?xml version="1.0"; encoding="utf-8" ?>
<ns:Test xmlns:ns="urn:testhierarchy:fcc">
<File_Header>
--<Record_ID>1</Record_ID>
--<Filler_S>01</Filler_S>
</File_Header>
<Batch_Header>
--<Record_ID>25</Record_ID>
--<Filler_S>20</Filler_S>
</Batch_Header>
<Payment_Record>
--<Record_ID>6</Record_ID>
--<Filler_S>22</Filler_S>
</Payment_Record>
</ns:Test>
i.e. Payment_Record and Batch_Header are at same level. I want Payment_Record under Batch_Header.
Kindly let me know if hierarchical structures can be handled in sender FCC. If yes then what should be the FCC parameters?
Thanks i.

Hi Minal,
We have Source structure same as yours. I am trying to use FCC to handle multiple hierarchy levels at sender side.
Can you please let me know if you have some solution for it?
Thanks,
Pooja.

File Sender FCC doesn't allow repetitive segments and unbounded together

File Sender FCC give me error if I use the repeatitive structure and * (Unbounded) together. Here is the recordset structure UNH,1,BGM,1,DTM,1,NAD,1,CNI,1,STS,1,RFF,*,DTM,1 for which I am getting the error "Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 12: missing structure(s) before type 'DTM' "
If I use the recordset structure UNH,1,BGM,1,DTM,1,NAD,1,CNI,1,STS,1,RFF,2,DTM,1 then I am able to parse the file. But My requirement is that I will expect variable no of RFF segments in my structure. If you guys could help me that would be great.

Hi Mohammad
In this case try to maintain the following in content conversion parameters.
Key Field Name = Key
<xml>.fieldFixedLengths = 1,......................
<xml>.fieldNames = Key,.................
<xml>.keyFieldValue = 1
<xml>.keyFieldInStructure = ignore
<xml>.endSeparator = ,
Think this should solve your problem.
Refer the following SAP help link :-
[http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm]
-Thanks
Karthik

Specify Starting Position in Sender FCC

Hi Experts Team,
I wish to specify the starting position of field in sender FCC.
can i????
regards,
kanda

Hi,
I think positions we can't identify with FCC statements. fieldfixedlengths itself system will identify automatically. If column have any specific character indication we can do easily. Check it according to your requirement.

Sender FCC for the following structure.

Hi,
I am using the following source structure:
<Goods> 0..unbounded(Data Type)
 <HeaderData>(1..1)
 <1>
 <2>
 <3>
 <ItemData>(1..unbounded)
 <10>
 <11>
 <12>
 <13>
 <n>
1:What will be the FCC details for the above structure?
2:Solution for the following error:
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: 'xml.documentName' is a mandatory parameter if more than one recordset per message is specifiedMandatory parameter 'xml.keyfieldName': no value found"
Regards,
Vishal.

P836340 wrote:>
> 1:What will be the FCC details for the above structure?
Document Name: your msg type
Document Offset:
Recordset Name:
Recordset Namespace:
Recordset Structure: HeaderData,1,ItemData,*
Recordset Sequence: Ascending\Descending
Recordset per Message: *
KeyField Name: give one value which u want to use as a key
KeyField Type: String(Case Sensitive)
header.fieldFixedLengths fix length according to your requirement eg: 2,2,2
header.keyFieldValue value of field which fixed as key field in header
header.fieldNames 1,2,3
body.fieldFixedLengths fix length according to your requiremen eg: 2,2,2,2
body.keyFieldValue 02 value of field which fixed as key field in item
body.fieldNames 10,11,12,13
> 2:Solution for the following error:
> "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: 'xml.documentName' is a mandatory parameter if more than one recordset per message is specifiedMandatory parameter 'xml.keyfieldName': no value found"
It is because you would have missed the values for the mandatory fields like documentName and keyfieldName
Thanks,
Arivarasu
Edited by: Arivarasu S on Aug 5, 2009 9:32 PM
Edited by: Arivarasu S on Aug 5, 2009 9:33 PM
Edited by: Arivarasu S on Aug 5, 2009 9:35 PM

Accessing Sender Agreement details in Module

Hi,
How can we access(read and then modify) the sender agreement details from SOAP header in from ModuleData in the Module interface?
One way I can think of is to read the SOAP message and parse it. The problem lies with accessing the SOAP message in the process method.
I would really appreciate your help.
Thanks.
SK

/people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
via that blog you can see how dynamic conf. is done ... via the dynamic conf. you can access mapping runtime too...

Reg sender contact details in form

Hi All,
How to find the sender contact details in a form?I want to get some fields from the structure SZA5_D0700.From which tables I will get this and what is field mapping for these data(sender address data).I am developing order confirmation form.where can I find mapping for sender contact details and address number.
I want to print at the footer of my form sender contact details.
Regards
Mahesh

Hi
Pass the order number to VBPA table and take the ADRNR field based on the
PARVW field and check his address details by passing into ADRC table and other ADR* tables
Regards
Anji

Sending contact details through sms

i need to know how to send contact details to some body by sms
Solved!
Go to Solution.

You can easily do this by downloading an app called Contact Share if it isn't already installed on your phone.

HT2188 I have a iphone4 lock phone, i don't know operating system please send me details imei no "012420005792680""

I have a iphone4 lock phone, i don't know operating system and network, please send me details. My phone imei no is "012420005792680"

This is a user to user technical support forum.
No one here would have access to the information you desire.

Plz anybody send complete details about webservices,enterprise portal

plz anybody send complete details about webservices,enterprise portal

Hi,
For Webservices,Go thru this Link,
http://help.sap.com/saphelp_nw04/helpdata/en/bb/c7423347dc488097ab705f7185c88f/frameset.htm
For Enterprise Portal,Go thru this Threads,
enterprise portal?
enterprise portal
Regards,
Padmam.

Please send the details of Notes-note-184754,407485

Hai
Please send the details of Notes-note-184754,407485 to [email protected]
I will assing the points
kumar

Hi check it here.
184754
Summary
Symptom
CAUTION: THIS NOTE WAS REPLACED. FOR MORE UP-TO-DATE, COMPREHENSIVE INFORMATION SEE NOTE 886102.
You want to copy a single BW System of a system group using a database copy. After the copy, you want to have a functional BW source system connection.
Refer to Note 325525. This helps you to select the correct procedure for your scenario. Also note that there are several ways to carry out the actual copy procedure. This is not covered in this note. Refer instead to the URL http://service.sap.com/solutionmanagerbp.
Other terms
Database copy, source system, BW, connection, refresh
Reason and Prerequisites
There are three scenarios:
1. You want to install a new BW (referred to below as "target BW") by copying an existing BW (referred to below as "original BW"). That is, you import the copy onto an empty computer.
2. You want to replace an existing BW (henceforth "old BW"), by copying a different BW (henceforth "original BW"). That is, a BW was already installed on the target host (the old BW). We will call the copy of the original BW "target BW". There are two different scenarios here:
a) You are still in the planning phase of this step, that is, you have not yet made the copy.
b) You have already overwritten the old BW with the copy of the other BW.
Solution
You must perform ONLY THE STEPS required for YOUR SCENARIO.
Scenario 1): In 1.2B, create a transport request in the original BW that contains all source system-dependent objects for all R/3 and DataMart source systems. The object types are ISMT, ISTT and ISTS. Note that the ISTS object (the transfer structure) may contain routines that must be transported as separate objects (Object Type ROUT).
As of BW 2. 0A, you are supported by the BW transport link, grouping "Backup for system copy". Select the R/3 and DataMart source systems in the source system filter and collect the source systems using the Drag and Drop function.
If you use type PSADELETE processes, also add these to the transport request.
Scenario 2)a): Create the described transport request in the old BW.
Scenario 2)a): In the old BW, delete all R/3 and DataMart source systems in the Administrator Workbench source system tree.
Scenario 1), 2)a) and 2)b): Import the copy.
Scenario 1), 2)a) and 2)b): In the target BW, change the contents of the "target host" field in all RFC connections (destinations) for R/3 and DataMart source systems (Transaction SM59) to a nonsensical, nonexistent address (such as 'nowhere'). Then, delete ALL R/3 and DataMart source systems in the Administrator Workbench source system tree. Caution: This step deletes all PSA tables of these source systems - the data is lost. A message is generated stating that the source system cannot be accessed (since you deleted the host of the RFC connection). Select "Ignore".
Scenario 2)b): Change to the source systems connected to the old BW and THERE delete the connection (in the source system) to BW. To do this, change to Transaction SE37 - RSAP_BIW_DISCONNECT function module Sngl. test. Parameter I_BIW_LOGSYS = <name of BW>, I_OLTP_LOGSYS = <name of the source system>, I_FORCE_DELETE = 'X'.
Scenario 1): If you want to connect the target BW to one or more source systems that are also connected to the original BW, assign a new logical system name (Table T000) to the target BW. However, we recommend that you follow Note 184447 when designing the system environment.
Scenario 2)a) and 2)b): Assign the same name to the target BW system that was assigned to the old BW system (logical system name, Table T000).
Scenario 1), 2)a) and 2)b): If you have just renamed the BW, execute Transaction BDLS to convert all relevant tables to the new logical system name. To do this, refer to Notes 121163 and 369758.
Scenario 1): Connect the required source systems. (Administrator Workbench - Source systems)
Scenario 2)a) and 2)b): Connect the source systems, that were connected to the old BW. (Administrator Workbench - Source systems)
Scenario 1) and 2)a): Import the request created above. Bear in mind the special CTS features for the source system-dependent objects (system changeability in connected systems; View V_RSLOGSYSMAP).
Scenario 2)b): Recreate the transfer structures/transfer rules and activate them.
Header Data
Release Status: Released for Customer
Released on: 20.03.2007 15:58:10
Priority: Correction with medium priority
Category: Consulting
Primary Component: BW-WHM-DST-SRC Source Systems
Releases
Release Independant
Related Notes
886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
733623 - Oracle export/import for BW system copies
524554 - Storing destinations in the BW environment
369758 - BDLS: New functions and better performance
325525 - Copying and renaming systems in a BW environment
127326 - CTS for InfoSources, update rules ...
121163 - BDLS: Converting logical system names

40785
Summary
Symptom
You are transporting BW objects that are heavily linked with each other so that several requests are necessary.Objects of a request are using objects which are locked on other requests.
In the target system, errors arise during the method execution of requests with BW objects (return code 8).The messages indicate that objects are required which do not exist in the target system and are also not contained on the request.
For example, you transport an object with attributes, but the attributes are not transported nor are they available in the system.In the log, message R7322 appears: 'Attribute &1 from characteristic &2 not (actively) available'. As a result, an InfoCube cannot be activated if InfoObjects are missing and so forth.
Additional key words
CTS, transport link, AWB, object collector
Cause and prerequisites
You collect objects with the transport link of the Administrator Workbench and then write these to a transport request.In the process, all objects which have not yet been transported are marked (development class $TMP). Or you install Business Content and write the installed objects directly to a request.
Objects with a different development class (not $TMP) are also gathered but they are not marked because the system assumes that these have already been transported and are then subject to automatic recording.If you are not sure whether these objects already exist in the target system, you can mark the objects.The system then writes them to the request and transports them (once again).
It could happen that objects that are locked on another request have been collected.You can recognize this by the column "Transport request" in the window with the collected objects (you may have to expand the tree with the collected objects completely). You should always release the requests beforehand, that means prior to the request that is being compiled.
This is because these objects are needed by objects that the system is now collecting, but do not yet reside in the target system or do not yet reside there in their most current version. If you import the request which the system is collecting prior to the other request, then the errors described in the symptom section of this note.
Solution
Proceed as follows if you are using the object collector:
Collect the objects
expand the tree with the collected objects completely
Release all requests that are displayed in the 'transport request' column.
Only then release the request with the objects that are being currently collected.
As of Support Package 16 this approach is simplified even further.In this case, a log with the following messages is displayed after writing the collected objects:
'Objects which are locked on a different transport request' (Message RS0305).If you expand this message, you receive a list of all objects which are locked on other requests.
'Transport requests which must be released first' (Message RS0306).If you expand this message, you receive a clear summary of the requests which must be released before the request currently being compiled.Here the system simply summarizes the requests from the previous list that still contain dependent objects.
Thus, as of Support Package 16 you no longer have to expand the tree completely and search for linked requests.
Source code corrections
Header Data
Release Status: Released for Customer
Released on: 05.09.2001 22:00:00
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BW-SYS Basis System and Installation
Secondary Components: BW-BEX Business Explorer
BW-WHM Data Warehouse Management
Releases
Release Independant
Highest Implemented Support Package
Support
Packages Release Package
Name
SAP_BW 20B SAPKW20B19
SAP_BW 20B SAPKW20B20
Related Notes
125499 - Activation error after transport of BW objects

Sender FCC ( File adapter ) limitations

Hi All,
 I have a Flat file on the sender side ..and i need to do the file content conversion .
I have doubts abt the File (FCC) adapter capabalities.Please let me know if i can build the following structure by using FCC
My Flat file will look some thing like this , I have all the header rows followed by all the detail rows followed by all the subdetail rows for all the details .
 HEADER1 fields
 HEADER2 fields
 DETAIL11 fields for HEADER1
 DETAIL21 fields for HEADER1
 DETAIL12 fields for HEADER2
 DETAIL22 fields for HEADER2
 SUBDETAIL111 fields for DETAIL11
 SUBDETAIL211 fields for DETAIL21
 SUBDETAIL121 fields for DETAIL12
 SUBDETAIL222 fields for DETAIL22
And i want to convert the flat file to the following format
 <HEADER1>
 <Filed1> ..</Field1>
 <Filed2> ..</Field2>
 <DETAIL1>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 <SUBDETAIL1>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 </SUBDETAIL1>
 <SUBDETAIL2>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 </SUBDETAIL2>
 </DETAIL1>
 <DETAIL2>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 <SUBDETAIL1>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 </SUBDETAIL1>
 <SUBDETAIL2>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 </SUBDETAIL2>
 </DETAIL2>
 <HEADER1>
 <HEADER2>
 <Filed1> ..</Field1>
 <Filed2> ..</Field2>
 <DETAIL1>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 <SUBDETAIL1>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 </SUBDETAIL1>
 <SUBDETAIL2>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 </SUBDETAIL2>
 </DETAIL1>
 <DETAIL2>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 <SUBDETAIL1>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 </SUBDETAIL1>
 <SUBDETAIL2>
 <Field1>..</Field1>
 <Filed2> ..</Field2>
 </SUBDETAIL2>
 </DETAIL2>
 <HEADER2>
Regards,
Tarun.

HI ,
 Thanks for the reply ..forgot to mention the top node .Below is the modified structure , Please tell me
if it is possible to get this structure using FCC.
Sourde Flat file :
HEADER1 fields
HEADER2 fields
DETAIL11 fields for HEADER1
DETAIL21 fields for HEADER1
DETAIL12 fields for HEADER2
DETAIL22 fields for HEADER2
SUBDETAIL111 fields for DETAIL11
SUBDETAIL211 fields for DETAIL21
SUBDETAIL121 fields for DETAIL12
SUBDETAIL222 fields for DETAIL22
Target File after FCC :
<root>
<HEADER1>
.........<Filed1> ..</Field1>
..........<Filed2> ..</Field2>
...............<DETAIL1>
......................<Field1>..</Field1>
......................<Filed2> ..</Field2>
...........................<SUBDETAIL1>
.................................<Field1>..</Field1>
.................................<Filed2> ..</Field2>
...........................</SUBDETAIL1>
...........................<SUBDETAIL2>
.................................<Field1>..</Field1>
.................................<Filed2> ..</Field2>
...........................</SUBDETAIL2>
...............</DETAIL1>
...............<DETAIL2>
....................<Field1>..</Field1>
....................<Filed2> ..</Field2>
.........................<SUBDETAIL1>
..............................<Field1>..</Field1>
..............................<Filed2> ..</Field2>
.........................</SUBDETAIL1>
.........................<SUBDETAIL2>
..............................<Field1>..</Field1>
..............................<Filed2> ..</Field2>
.........................</SUBDETAIL2>
..............</DETAIL2>
<HEADER1>
<HEADER2>
.........<Filed1> ..</Field1>
..........<Filed2> ..</Field2>
...............<DETAIL1>
......................<Field1>..</Field1>
......................<Filed2> ..</Field2>
...........................<SUBDETAIL1>
.................................<Field1>..</Field1>
.................................<Filed2> ..</Field2>
...........................</SUBDETAIL1>
...........................<SUBDETAIL2>
.................................<Field1>..</Field1>
.................................<Filed2> ..</Field2>
...........................</SUBDETAIL2>
...............</DETAIL1>
...............<DETAIL2>
....................<Field1>..</Field1>
....................<Filed2> ..</Field2>
.........................<SUBDETAIL1>
..............................<Field1>..</Field1>
..............................<Filed2> ..</Field2>
.........................</SUBDETAIL1>
.........................<SUBDETAIL2>
..............................<Field1>..</Field1>
..............................<Filed2> ..</Field2>
.........................</SUBDETAIL2>
..............</DETAIL2>
<HEADER2>
</root>
Regards,
Tarun.

Seeburger AS2/EDI sender configuration details

Hello All,
I am working in EDI interface for ANSI X12 using Seeburger AS2/EDI , As I am new to B2B interface I have one doubt regarding Transaction set identifier code,interchange sender and receiver ID , In case of B2B add on it is clearly configured on EDISeparator Sender Adapter under filter
but in case of Seeburger AS2/EDI I am not understanding where we can add this details ,
Thanking you
Sridhar

Hello Sridhar,
for incoming data, the Seeburger BIC-Adapter uses a mapping in the Module-Chain which automatically detects the following parameters
- MessageType and Version (e.g. ANSIX12_850_V4010) from ST segment
- Interchange Sender ID (from ISA segment)
And the MessageSplitter then allows to forward each combination to a specific SenderAgreement for processing the data in PI.
This example shows an entry in the "MessageSplitter" that assigns an 850 V4010 message from a partner with the Sender ID 11111111111 to a specific SenderAgreement to process the data...
Kind Regards
Stefan

Sender FCC Details

Similar Messages

Maybe you are looking for