FM for ACC_BILLING IDOC

hi all,
I have a senerio that i have to Make the ACC_BILLING IDOCs as outbound for EDI Connection. So May i know what is the Function module for the IDOCs for OUTBOUND. and I also wanna to the Function Module for ACC_INVOICE for OUTBOUND processing. I want to make the function module for process code. and can any one tell me whether the acc_billing and acc_invoice idocs can be process as out bound.
thanks in advance
manas

Hi,
Call Rev. Rec. Billing Function Module
    call function 'SD_REV_REC_BILLING'
         exporting
              fis_vbrk     = vbrk
              fif_dummy_nr = document_old
              fis_t001     = t001
              fif_posnr    = lif_posnr
              fif_comp     = i_comp
         tables
              fit_xaccit   = xaccit
              fit_xacccr   = xacccr
              fit_xvbrp    = xvbrp
              fit_xkomv    = xkomv
              fit_xacchd   = xacchd
              fit_rr_accit = rr_accit
              fit_rr_acccr = rr_acccr
              fit_xfplt    = xfplt
              fit_xvbpa    = xvbpa
         exceptions
              error_01     = 01.

Similar Messages

FM for ACC_BILLING and ACC_INVOICE

hi all,
I have a senerio that i have to Make the ACC_BILLING IDOCs as outbound for EDI Connection. So May i know what is the Function module for the IDOCs for OUTBOUND. and I also wanna to the Function Module for ACC_INVOICE for OUTBOUND processing. I want to make the function module for process code. and can any one tell me whether the acc_billing and acc_invoice idocs can be process as out bound.
thanks in advance
manas

If your requirement to have a pricing procedure to meet this requirement, try as follows:-
100:::PR00::::Base Price
110:::ZSER::::Service Tax::::100
120:::JECS::::Ecess::::::::::::::110:::::::110
130:::JA1X::::SHECess:::::::::110:::::::110
140:::BVAT::: (Not clear what is this)
150:::JIN7::::Vat:::::::::::::::::::::140:::::::140
In this, if you want to levy ED also, then you need to insert appropriately in the above
thanks
G. Lakshmipathi

Program does not create PCP0 documents for TMS Idocs

Hi All,
We have a dialy job that will catch up all payroll/tms idocs that is being received by the system. The program will automatically creates a document in the tcode PCP0 for every idocs that it has gathered both Idocs that have no errors and Idocs that have errors. Would like to ask if you have experienced the cause of this?
Regards,
S. T.

Hi wyo3witt,
I checked your account and saw that your subscription had been canceled, but that you hadn't been refunded yet. I processed a refund for you (transaction ID 0066152640); you see it in your account in 2-3 days.
Best,
Sara

One file for multiple IDOCs

Hi,
Need help on IDOC files created on application server.
For IDOCs of EDI type generally one file is created on application server for one idoc. Is there any way to create a common file for multiple IDOCs that are created in a batch job?
Thanking in anticipation
Sudhir Bhate

Hi Sudhir;
Yes, it is a setting on the outbound parameters of the partner profile. In the section for "output mode," select "Collect IDocs." This link to help.sap.com describes the procedure:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b812a43d711d1893e0000e8323c4f/content.htm
Cheers,
John

IDoc type could not be determined for the IDoc

I am trying to Post the payment run through the transaction F110.
In the payment run log i get the following message:
"IDoc type could not be determined for the IDoc"
But in fact the IDoc is generated and it is displayed in We05.
I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
Has anybody Idea about why this error is coming and how i can resolve this?
This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
Would appreciate if anyone can please help on the same.
Thanks & Regards,
Narayanan

Hi,
If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
still if you are having any problem
Check in the below path:
IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
2. Assign Release Approval Procedure for Release for Payment
3. Define Users with Authorization to Payment Release
Thanks
Chandra

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

How to find the appropriate user exit for invoic02 idoc in idoc_output_invo

Hi all,
I am new to this community p
i have issue regarding the How to find the appropriate user exit for invoic02 idoc in idoc_output_invoic function module.........
thanks,

Hi ,
welcome to SDN.
You can select the appropriate Customer exit accrding to the available parameters .
The list of exits available are
EXIT_SAPLVEDF_001
EXIT_SAPLVEDF_002
EXIT_SAPLVEDF_003
EXIT_SAPLVEDF_004
For Example , if you want to modify the Idoc data(EDIDD) you have to use the EXIT_SAPLVEDF_002. accodingly you can select the user exit according to the avaialable parametres.Use Table MODSAP fto get the Enhancement name.
Hope this Helps
Rgds
Sree
Edited by: Sree on Jul 23, 2010 12:11 PM

How to find out the table, data for the IDOCS is pulled from?

HI
The ZFPH9999397 VENDOR FEED job runs the RBDMIDOC program with the variant Z9999_397. This creates IDOCS that are sent out and eventually wind up in IMOS.
The IDOC Type is CREMAS.
Can you tell me which table or tables the data for these IDOCS is pulled from?
Or tell me the procedure to find out the table name.
Thanks,
das.
Edited by: sathish dasari on Dec 10, 2009 11:54 AM

You can use Transp. Table      TBD62 .
enter Message Type                      CREMAS
you will get the list of tables and the fields from which data is pulled based on the change pointers in Transp. Table      BDCP.

How to find out the printer name for the Idoc

Hi guys
I want to find out the printer name for the Idoc,,some default printer is attached for one idoc,then how can we see the printer name for this idoc.
Regards
Madhoo

Hi,
For ALE/IDOC the medium will be either ALE or EDI but not printer.So it might be wrongly attached.As such there won't be any printer attached to idoc.
Regards,
Nagaraj

Creation of New Message Type for Extended IDoc

Dear Friends,
I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
for Change Pointers.
Warm Regards,
Naveen Mutyapu.

Hi naveen mutyapu,
see these links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
happy learning.
thanks
karthik

How to Configure logical path and how to retrieve physical path for an IDOC

Hi ,
I want to configure logical path for an IDOC,
and then I need to retrieve Physical path from this logical path
using a FM (eg. FILE_GET_NAME).
How to configure the logical path for an idoc ?
Regards ,
Harshit Rungta

Using Logical Files in ABAP Programs
To create a physical file name from a logical file name in your ABAP programs, use the function module FILE_GET_NAME. To insert the function module call in your program, choose Edit ® Insert statement from the ABAP Editor screen. A dialog box appears. Select Call Function and enter FILE_GET_NAME. The parameters of this function module are listed below.
Import parameters
Parameters
Function
CLIENT
The maintenance tables for the logical files and paths are client-dependent. Therefore, the desired client can be imported. The current client is stored in the system field SY-MANDT.
LOGICAL_FILENAME
Enter the logical file name in upper case letters that you want to convert.
OPERATING_SYSTEM
You can import any operating system that is contained in the list in Transaction SF04 (see Assigning Operating Systems to Syntax Groups). The physical file name will be created according to the syntax group to which the operating system is linked. The default parameter is the value of the system field
SY-OPSYS.
PARAMETER_1
PARAMETER_2
If you specify these import parameters, the reserved words in the physical path names will be replaced by the imported values.
USE_PRESENTATION
_SERVER
With this flag you can decide whether to import the operating system of the presentation server instead of the operating system imported by the parameter OPERATING_SYSTEM.
WITH_FILE_EXTENSION
If you set this flag unequal to SPACE, the file format defined for the logical file name is appended to the physical file name.
Export Parameters
Parameters
Function
EMERGENCY_FLAG
If this parameter is unequal to SPACE, no physical name is defined in the logical path. An emergency physical name was created from table FILENAME and profile parameter DIR_GLOBAL.
FILE_FORMAT
This parameter is the file format defined for the logical file name. You can use this parameter, for example, to decide in which mode the file should be opened.
FILE_NAME
This parameter is the physical file name that you can use with the ABAP statements for working with files.
Exception Parameters
Parameters
Function
FILE_NOT_FOUND
This exception is raised if the logical file is not defined.
OTHERS
This exception is raised if other errors occur.
Suppose the logical file MYTEMP and the logical path TMP_SUB are defined as in the preceding topics and we have the following program:
DATA: FLAG,
      FORMAT(3),
      FNAME(60).
WRITE SY-OPSYS.
CALL FUNCTION 'FILE_GET_NAME'
     EXPORTING
          LOGICAL_FILENAME        = 'MYTEMP'
          OPERATING_SYSTEM        = SY-OPSYS
          PARAMETER_1             = '01'
     IMPORTING
          EMERGENCY_FLAG          = FLAG
          FILE_FORMAT             = FORMAT
          FILE_NAME               = FNAME
     EXCEPTIONS
          FILE_NOT_FOUND          = 1
          OTHERS                  = 2.
IF SY-SUBRC = 0.
WRITE: / 'Flag      :', FLAG,
         / 'Format    :', FORMAT,
         / 'Phys. Name:', FNAME.
ENDIF.
The output appears as follows:
HP-UX
FLAG :
FORMAT : BIN
Phys. Name: /tmp/TEST01
In this example, the R/3 System is running under the operating system HP-UX, which is member of the syntax group UNIX. The logical file name MYTEMP with the logical path TMP_SUB is converted into a physical file name /tmp/TEST01 as defined for the syntax group UNIX. The field FNAME can be used in the further flow of the program to work with file TEST01 in directory /tmp.
Suppose we have a logical file name EMPTY with the physical file name TEST, connected to a logical path that has no specification of a physical path. If you replace the EXPORTING parameter 'MYTEMP' with 'EMPTY' in the above example, the output appears as follows:
HP-UX
FLAG : X
FORMAT :
Phys. Name: /usr/sap/S11/SYS/global/TEST
The system created an emergency file name, whose path depends on the installation of the current R/3 System.

Best practice for migrating IDOCs?

Subject: Best practice for migrating IDOC's?
Hi,
I need to migrate some IDOC's to another system for 'historical reference'.
However, I don't want to move them using the regular setup as I don't want the inbound processing to be triggered.
The data that was created in the original system by the processed IDOC's will be migrated to the new system using migration workbench. I only need to migrate the IDOC's as-is due to legal requirements.
What is the best way to do this? I can see three solutions:
A) Download IDOC table contents to a local file and upload them in the new system. Quick and dirty approach, but it might also be a bit risky.
B) Use LSMW. However, I'm not sure whether this is feasible for IDOC's.
C) Using ALE and setting up a custom partner profile where inbound processing only writes the IDOC's to the database. Send the IDOC's from legacy to the new system. Using standard functionality in this way seems to me to be the best solution, but I need to make sure that the IDOC's once migration will get the same status as they had in the old system.
Any help/input will be appreciated
Regards
Karl Johan
PS. For anyone interested in the business case: Within EU the utility market was deregulated a few years ago, so that any customer can buy electricity from any supplier. When a customer switches supplier this is handled via EDI, in SAP using ALE and IDOC's. I'm working on a merger between two utility companies and for legal reasons we need to move the IDOC's. Any other data is migrated using migration workbench for IS-U.

Hi Daniele
I am not entirely sure, what you are asking, Please could you provide additional information.
Are you looking for best practice recommendations for Governance, for example: Change transports between DEV, QA and PRD in BPC 7.0?
What is the best method? Server Manager backup and restore, etc ?
And
Best Practice recommendations on how to upgrade to a different version of BPC, for example: Upgrading from BPC 7.0 to 7.5 or 10.0 ?
Kind Regards
Daniel

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

How to find out what are all the change pointers assoicated for an idoc ??

Hi ,
How to find out what are all the change pointers activated for an idoc ??
Thanks,
Varma

Verma,
You can check what are the active Change Pointers for the message type in tcode BD50
Use tcode BD61 to check whether change pointers are active or not??
Hope this helps..

How to get Get IDOC Number for Inbound IDOCS

Hi,
I am using the FM -- IDOC_INPUT_HRMD for creating Inbound IDOCS.
I populate the values for Control Record and Data Record and the IDOC is posted successfully and i get the status 53 in the status Table.
But the problem is the field for IDOC number(DOCNUM in IDOC_STATUS Table of the FM ) is empty.
How can i get the DOCNUM for the IDOC posted as a result of this FM ?
regards,
Siddhartha

Hi Siddhartha,
I think you cannot call IDOC_INPUT_HRMD fm directly from the external program as this fm only handles the application logic part and not the idoc number generation and save part.
So I think you have to call IDOC_INBOUND_SINGLE from your external program and then get the IDOC number.
Then if you need the status records then you need to call another fm and feed IDOC number that you have got from IDOC_INBOUND_SINGLE (there is one IDOC_READ_COMPLETELY but it is not a remote enabled fm)
OK, I just found one RFC enabled fm which you can use,
EDI_DOCUMENT_READ_ALL_STATUS
Hope this helps..
Sri
Message was edited by: Srikanth Pinnamaneni

FM for ACC_BILLING IDOC

Similar Messages

Maybe you are looking for