EDI 823 (Inbound) - Field Mapping

Hello,
I need to configure Incoming IDOC EDI 823 for Lockbox.
Basic type: FINSTA01
Message Type: FINSTA
Processing code: FINS
Function Module: IDOC_INPUT_FINSTA
By giving the Basic type u2013 FINSTA01 and executed in the test tool, I am getting the list of all the segments related to this Idoc type.
I request please let me know how I can map the field segments by taking minimum segments and what qualifiers should I input to process the idoc.
Thanks for your co-operation.

No Response.

Similar Messages

EDI 823 inbound lockbox

Hello all,
I am using idoc_input_lockbox fm to process finsta01 idocs generated based on EDI 823 format. I am having a custom field in AVIK, payment advice header table which needs to be populated with the 3 fields from the idoc concatenated. Is EXIT_SAPLIEDP_202 right place to do this? I am moving the fields I need from the corresponding segments into the custom field of AVIK and updating idoc_avik parameter with this.

No Response.

Inbound EDI 823

Hi Guys,
I'm working on EDI 823 inbound file to SAP. Appreciate if u have any document for mapping EDI 823 (IDOC FINSTA01) to SAP.
u can mail me at [email protected]
really appreciate it....

Hi Rams,
We really need it. can you send it please.
Thanks & Regards,
Raj

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

Mapping error for EDI 823 from XI to R/3

Hi All,
We are receiving an EDI 823 from XI to R/3 and the XML file looks like this as below.
Partner No: YRDCLNT110
Partn Type: LS
Sender Information
Port: SAPYXD
Partner No: EXTD_BALE
Partn Type: LS
Whereas there exists no partner no. in R/3 by the name EXTD_BALE. The interesting part is EXTD_BALE is a IDoc Adapter Port No in XI.
Please provide inputs on these.
Regards,
Karthik

Hi Karthik,
Have u configure a R/3 port in IDX1 of XI. This port has the RFC destination pointing to R/3. It will be used by XI to get into R/3.
Regards,
Akshay

Mapping Issue for EDI 823 from XI to R/3

Hi All,
We are receiving an EDI 823 from XI to R/3 and the XML file looks like this as below.
- <FINSTA01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<MANDT>110</MANDT>
<DOCNUM>0000000000000000</DOCNUM>
<DIRECT>1</DIRECT>
<IDOCTYP>FINSTA01</IDOCTYP>
<MESTYP>LOCKBX</MESTYP>
<STD>X</STD>
<STDVRS>003040</STDVRS>
<STDMES>823</STDMES>
<SNDPOR>EXTD_BALE</SNDPOR>
<SNDPRT>B</SNDPRT>
<SNDPRN>1000000015</SNDPRN>
<SNDSAD>1000000015</SNDSAD>
<RCVPOR>SAPYRD</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>YRDCLNT110</RCVPRN>
</EDI_DC40>
Now the problem is the incoming IDOC ends up with errors.
Recipient Information
Port : <empty>
Partner No: YRDCLNT110
Partn Type: LS
Sender Information
Port: SAPYXD
Partner No: EXTD_BALE
Partn Type: LS
Whereas there exists no partner no. in R/3 by the name EXTD_BALE. The interesting part is EXTD_BALE is a IDoc Adapter Port No in XI.
Please provide inputs on these.
Regards,
Karthik

Hi, any feedback in this one ?

EDI 823 to iDoc FINSTA01

I am trying to map EDI 823 file to iDoc FINSTA01.
I mapped as much as I know, but I am getting following errors when I test it:
- External transaction is missing for determining the posting rule
- Bank statement date is incorrect: 00000000
Anyone seem these errors?
Anyone know what I need to fix to get rid of these errors?
Any help can be really appreciated.
Thank you,
John

Hi,
Can you give the procedure to configure EDI 823 and the bare minimim segments with fields that are required to be filled if you have solved the issue you got earlier.
Thanks & regards,
raj

Lockbox with EDI 823

Here is the process we follow:
We get EDi823 from the Bank. we create the I-doc FINSTA01 which creates the data in the Payment advice. The customer pays by 2 fields- Actual Invoice number and reference which is a sales order number.
What are the settings we require in the Selection rule or FLBP to check for both the fields? we created a new selection field with Document number and Reference field and attached it to the customer master but that is not working and FLBP is putting everything "on Account".
Any Suggestions.

Hi Nitin
When you create the selection rule, you can prioritize the fields. In your case, document number should be first and then the reference.
Also, in the config for selection rule, the system gives the options for external selection filed and the selection field. So, you need to take a look at the payment advice and confirm that the document number is getting populated in the BELNR field of the payment advice and the order number is actually getting populated in XBLNR.
If you EDI 823 is mapped to populate the above values in some other fields in the payment advice, your config should reflect the same. Otherwise the system would not match the open items.

Payment Advcie - EDI 823 (Lockbox - Incoming Payment)

Hello,
In process of testing EDI 823(Lockbox u2013 Incoming Payments) using testtool, Idocs are been successfully processing when an attempt is made to post the incoming customeru2019s payment for an open invoice (Basic type u2013 FINSTA01, Message type u2013 LOCKBX). Payment advice note is being generated for the successful processed Idocs.
Then we ran a report RFAVIS40 in SE38 which basically selects the payments advices and then posts the clearing document. In the process when we are trying to execute the report for the generated payment advices u201CFor document type DZ, an entry is required in field referenceu201D this is the message we are getting.
Manually I execute the same payment advice number using FBE2. When I enter the info in u2018Payment totalu2019 and u2018Payment doc.nou2019. at the Header level of FBE2 and then I run the report again, invoice documents are getting cleared.
What config settings require to automate this functionality? OR Am I missing any mandatory field information at the time I process Idoc? OR System would work only in this manner?
Please pass your comments.
Thanks.

Hi,
Have never worked with EDI earlier so have some basic questions.
We have an interface for incoming payments. The idea is that the incoming EDI IDOC interface would clear the open items in the customer account.
Initially, have planned to use PEXR200/ REMADV, but realised that it is for creation of a payment advice. Can i use this to clear post and accounting doc or clear an open item in the customer account.
Is there any other IDOC that i can use.
thanks in advance

EDI message to IDOC mapping

hi
is there a place where i can find mapping of EDI messages to that of SAP IDOC message types?
~Suresh

Hi Suresh,
EDI subsystem will convert the IDOC into flat file (X12, EDIFACT, ODETTE, VDA etc) or flat file into IDOC. At the EDI subsytem the there will be field mapping instructions design will be there which maps the idoc to flat file. So its EDI subsystem which will be used identify the idoc msg types. Which subsystem u are using.
Regards
kannaiah

How to develop Standard Inbound 856 Map???.

Hi Team,
We are trying to develop a standard inbound 856 map in Biztalk 2010. But unable to fetch the data from S-Level i.e. Shipment level ,E-Level (Equipment),O-Level(Order) and so on to the output.
So can you please provide a sample Standard inbound 856 map with clear idea for mapping 856 map.

Hi Leonid,
856 map means I have used existing schema for 4010_856 message i.e. Shipment message in the path-
C:\Program Files (x86)\Microsoft BizTalk Server 2010\XSD_Schema\EDI\MicrosoftEdiXSDTemplates\X12\00401\X12_00401_856.xsd for creating a map.
Here Inbound incidents I have used X12_00401_856 schema in the source.

How to add a new field in the Field Mapping

Dear Freinds,
               I have two un used fields in the Source fields to the Target Fields ,
i have to add the 3   fields which r there in the my source fields to that
of the target fields ( as per the change in the requirement) in the 5th Step
i.e Maintain Field Mapping and Conversion Rules
the Target strucutre & the Source fields( by clicking the button
Source field and selcting the fields from the popup menu) in the mapping and conversion step ,i want to add 3 fields which are availabe in the list of th source list which i want to map to the Target strucutre .
When i tried it is adding in the othe target field
presently i have mapping (5th sept ) as below.
   ZPA30_08                       LSMW
       Fields
           TABNAME                      Table Name
                               Source: ZP0008_STRC-PERNR (Personnel Number)
                               Rule :   Default Settings
                               Code:    ZPA30_08-TABNAME = 'ZPA30_08'.
           TCODE                        Transaction Code
                               Rule :   Default Settings
                               Code:    ZPA30_08-TCODE = 'PA30'.
now i want to add 3 fields Pernr,wage type and Amount , but when iam trying it is
getting and saved in the TABNAME .
How can i map please let me know .
Regards
syamla

Hi,
So you need that this new field have data in old records?
1.- If you are in BI 7.0 and the logic or data for that New field are in the same Dimension, you can use a Remodeling to fill it. I mean if you want if you want to load from a Master Data from other InfoObject in the same Dim.
2.- If condition "1" is not yours.
First add the new field, then create a Backup Cube (both cubes with the new field) and make a full update with all information in the original Cube. The new field willl be empty in both cubes.
Create an UR from BackUp_Cube to Original_Cube with all direct mapping and create a logic in the Start Routine of the UR (modiying the data_package) you can look for the data in the DSO that you often use to load.
To do that both cubes have to be Datasources ( right click on Cube-> aditional function-> and I think is "Extract Datasource")
Hope it helps. Regards, Federico

In XI Mapping multiple fields mapping to single target field.

Hi Friends,
In XI Mapping multiple fields mapping to single target field.
For example my requirement is :
Source Fields:(This RFC BAPI Structure)
Empno                0-1
EmpName           0-1
Address             0-1
Taget Field is:
Details               0-1
The above three fields passed to the Details Field. Here i am using Concat function
But i have one query on that on,Every field having "line Break" required.
Can you please help me out above this requirement.
Thanks in Advance,
Sateesh N.

If you want a line break between the three fields, then try
passing a,b,c to the udf and in the udf you would have
return a+"\n"+b+"\n"+c;

ABAP code which will use function module during field mapping in LSMW

Hi,
During field mapping in LSMW, for one of the field called field, I want to use a function module 'QF05_RANDOM_INTEGER', which will generate random numbers and map that random number to that field.
How do I write ABAP code which uses function module, during filed mapping for a particluar field in LSMW ?
Please help...
Regards,
Tushar.

Hi Tushar,
You can write in FORM ROUTINE and LSMW.
I hope you know how to write ABAP code at field level.
If not ...
Come to change mode->select the field->Rule->ABAP Code
write a perform statement in ABAP code at field level.
<b>PERFORM test</b> using val
             changing valu.
Go to Utilities(at menu)->switch layout-> extras ->select Layout->check Form routine-> it will display a FORM Routine... at bottom
this is the place where you can write some code for
<b> FORM test</b> using value
          changing value1
FM call....
.ENDFORM
Get the value1 returned and use for the Field population.
Reward points if this Helps.
Manish
Message was edited by:
        Manish Kumar

How to create Rules with Flex Field mapping in the bpm worklist

I Have created a flex field label and was able to map to the flex field attributes .
But when i try to create a rules , I don't see the label or the flex attributes in the task payload .
Can someone please help is understanding how to create Rules with Flex Field mapping in the bpm worklist .
Even I am also searching for any scripts which will take the flex fields prompts and can directly create a label in the bpm worklist .
Any pointers or suggestion is highly appreciated .

Hi,
SE38 -> Enter program
Select Variants button and display. In the next screen, enter a variant name, (If not existing , press Create to create new one), else click on Change.
Now the selection screen will display with a button "Variant Attributes" at the top.
Click on that button.
In the next screen, go to the selection variable column of the date field. Press F4 or drop down and select 'D' for date maintenance.
In the column "Name of Variable (Input Only Using F4)" press F4 or drop down, select whichever kind of date calculation you want and save the variant.
Now whenever you run the prgrm with this variant, date will be displayed by default.
Regards,
Subramanian

EDI 823 (Inbound) - Field Mapping

Similar Messages

Maybe you are looking for