topic Re: ALE for Invoice Posting in Application Development and Automation Discussions

ALE for Invoice Posting

former_member125661 — Mon, 02 Jun 2008 14:46:06 GMT

I have Invoice data coming from a 3rd party system and storing in a folder in application server.

I am planning to read this data and use ALE to do a invoice posting similar to F-43 (Not FB60) .

Please advice how to go about this.

I tried to create a partner profile of type US instead of LS(Logical system).

Created my own trfc port.

Put message type INVOIC in the inbound parameters of the partner profile. Assigned the process code MR01 and used the option trigger immediately. I am not sure if INVOIC is the right message type for F-43.(if there is any other message type?)

I wanted to test this somehow. I activated the change pointer for INVOIC in BD50, then changed an existing Invoice in F-43. and ran We02 to see if any idocs are created for outbound ( Temporarily, i even set up outbound parameters for message type INVOIC). No idocs were generated. I even tested the partner profile using the program RSECHK07. It seemed ok.

Re: ALE for Invoice Posting

Former Member — Mon, 02 Jun 2008 14:58:01 GMT

It seems u have created a file in application server with the data comming from the 3rd party system, but that data is supposed to be processed first and a idoc is then generated from that file

Run this is program RSEINB00 with the file path and your file port.

Hope this helps you if i got you correct

Regards

Re: ALE for Invoice Posting

former_member125661 — Mon, 02 Jun 2008 15:02:52 GMT

I dont think u got me right. I am not using EDI and file port. My data in application server is just a random ASCI file. I am writing a custom program to read this file and convert them into IDOCs .I am going to write a program to read these files and convert the data there into IDOC using the FM 'IDOC_INBOUND_ASYNCHRONOUS' .

But before I do all these, I wanted to make sure that I am using the right message type - INVOIC for F-43.

Also I am not sure if I have to use a std. process code MR01 or use create a custom one and then assign any FM in we42.