Interface Type "ABAP Dictionary-Based Interface" not generating Interac

Hi All,
I am getting problem in ABAP Adobe interactive forms in ECC6.
I tried designing Adobe interactive form by 2 following ways:
1) in SFP -->> Interface Type -->"ABAP Dictionary-Based Interface"
2) in SFP -->> Interface Type -->"XML Schema-Based Interface"
When I designed with 1st way I am not getting Interactive form, I get only read
only form when executing ABAP webdynpro application.
But same form giving interactive form when calling ABAP program.
But when I designed with 2nd(XML) way I am getting Interactive form. In Webdynpro application.
In both case i have kept view property as enabled.
Please guide me, Is there any step which is mandatory for Adobe interactive forms when
we use (SFP -->> Interface Type -->"ABAP Dictionary-Based Interface"), with ABAP webdynpro application.
Thanks

XML Schema-Based Interface

Similar Messages

Message Interfaces in ABAP Dictionary?

Hi,
I have imported an IDOC from R/3 into my XI System. Does anybody know where the structure of my imported IDOC is saved? Will this Idoc be mapped to some Dictionary structures? Where is the structure of the IDOC saved in XI?
rg,
markus

The structure of the idoc will be saved in SWC->Imported objects->IDocs.
Regards,
Divija.

Generate Adobe Interactive Form with XML Schema-Based Interface

Hi,
I need to generate a adobe Interactive but with XML Schema-Based Interface, i have one example but with ABAP Dictionary-Based Interface.
CALL FUNCTION 'FP_JOB_OPEN'
CHANGING
    ie_outputparams       = fp_outputparams
* EXCEPTIONS
*   CANCEL                = 1
*   USAGE_ERROR           = 2
*   SYSTEM_ERROR          = 3
*   INTERNAL_ERROR        = 4
*   OTHERS                = 5
CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
EXPORTING
    i_name     = 'ZMMDM_CL'
IMPORTING
    e_funcname = fm_name.
But when i call the next function for print i need the docxml parameter and i don't know how to get it
fm_name
CALL FUNCTION fm_name
EXPORTING
   /1BCDWB/DOCPARAMS        = fp_docparams
*    /1bcdwb/docxml           =
* IMPORTING
*   /1BCDWB/FORMOUTPUT       =
* EXCEPTIONS
*   USAGE_ERROR              = 1
*   SYSTEM_ERROR             = 2
*   INTERNAL_ERROR           = 3
*   OTHERS                   = 4

1) this questions was asked many times before, you didn´t search for a second
2) I am not aware of any standard solution
3) custom solution: use XSLT transformation ID to get XML from the filled DDIC structure and use string operations to add the header and footer to create a valid XML.
Regards Otto

Re: Adobe forms - interface type

Hi...
    When Iam creating the interface ... it is asking Description and
                                           interface type as         ABAPDictionary- Based interface
                                                                            XML Scheme- Based Interface
                                                                         Smartforms-Compatible interface...    Have to select one option.. In some Examples I didnt see this interface type Option... what is the use of this interface type...
Thanks & Regards,
Abaper..

hello again,
i tried to list all the things u need to know to create your interface:
1.      Open the required interface in the Repository Browser of the ABAP Workbench.
2.      The Interface tab is displayed. Under Form Interface, double-click the Import node
3.      You see a screen for entering import parameters. This screen also shows the standard parameter /1BCDWB/DOCPARAMS. You cannot change this parameter.
You use this parameter in your application program, to specify the value for the language setting, for example. To display this structure in the ABAP Dictionary, double-click the SFPDOCPARAMS type.
4.      XML schema-based interface
○     The standard parameter /1BCDWB/DOCXML with the type XSTRING is used for sending data from the application program.
ABAP-based or Smart-Forms-compatible interface
○     To insert a new line, choose Insert Line (This graphic is explained in the accompanying text). Enter the parameter names of the data you want to import. These names are valid for the whole form and do not have to match the variable names in the data collection program. All data types are valid. TYPE can be selected under Type Assignment.
5.      When you double-click Export, you see the standard parameter /1BCDWB/FORMOUTPUT of the generated function module. You cannot change this parameter.
Note: You use this parameter in your application program, to make the generated form available as a PDF for further processing, for example.
6.      To display the exceptions used by the generated function module, double-click Exceptions.
7.      Activate the interface.
Note: At runtime, the application program must provide the parameters. If a parameter has been defined in the form, but is not defined when the application program is called, then the output of the form ends with the program crashing (hex dump).
However, it is also possible that the application program provides parameters that the form does not need. You do not need to mention these parameters in the form; they can also be specified in a different order from the code of the application program. This has the advantage that an application program can work with several different forms.
Hope this helps
Cheers

MRP Planned % Safety Stock Not Generating Supply in R12 ASCP

Playing with MRP Planned Safety Stock in an unconstrained plan. See safety stock in the horizontal plan. See safety stock in the pegging tree. Yet this type of safety stock is not generating any supply recommendations. However with "regular fixed quantity" safety stock the plan is. Thanks in advance.

Hi
If I understand your qn correctly., user defined SS is working and MRP planned % is not. Have you setup MRP planned % such that you gave the SS method., bucket days and % for the item attributes?
Also make sure that you have demand for the item since it looks at your demand in future,adds up demand within the bucket days and applies the % .
Thnx
Partha

Data view not showing XML schema based Interface

Hi Experts,
I am trying to create a Interactive adobe form by following a step-by-step tutorial.The steps I have followed :
1. Created a WD ABAP component with just one field.
2. Created the context node and also an atribue for PDF Source.
3. Add an Interacive form UI element.
4. Activated the View.
5. Add template source and assigned the context node to generate a XML based interface.
6. It created Interface successfully.
7. But when I open the Adobe form, the context fields are not showing in data view as data sructure..
What could possibly be the reason for it. Please guide me why data structure is not showing.
Thanks and Regards
Sanket

Hello Snikat
Can you please give a brief how did yu solved this problem.. I'm also facing similar issue.
Thanks
Ajay

Is there "Interface Type Node" present in WD JAVA as in WD ABAP ?

Hi,
Experts,
As i have gone through WD ABAP in that i found "Interface Type Node" under Context tab but i have a dought is that type "Interface Type Node" is present in WD JAVA or not.If not why and its use ?
Thank You,
Shabeer Ahmed.

Hi,
There is no "Interface Type Node" exists in WD4J as we can create the node in the Interface controller and map it component controller.
In WD4A we cannot create node under Interface Controller, we have to create the Interface Type Node in component controller then it automatically gets create in Interface Controller also.
The Interface Type Node is used to exchange the data between the two WebDynrpo components.
Thanks,
Jhansi Miryala

ABAP Dictionary type FLTP is not allowed for screen element

Hi Experts
I tried to open VBFA in se16 and i got the message in the status bar like this , what does it mean. please explain.
"ABAP Dictionary type FLTP is not allowed for screen element"

Hi,
This is from help
ABAP Dictionary type FLTP is not allowed for screen element
Message no. 37048
Diagnosis
The format of the ABAP Dictionary field is only for use within the ABAP
program and cannot be used in the Screen Painter.
Procedure
The field cannot be used in screens. If you want to output the
information in the field or assign a value to the field from the screen,
you must use an intermediate field with an appropriate format.
Reward points
Regards

The interface type is valid, but the specified interface number is not configured

Hi
I'm all new to using LabVIEW, which I have to use for a project. I'm trying to make a setup with a Keithley 2000 multimeter and an Agilent U2722A SMU. But I can't figure out how to get these instruments to communicate with LabVIEW. I can see and send commands to the Keithley 2000, but not the Agilent U2722A, with Agilent Connection Expert. But when I use LabVIEW I can't see any of them, and if I use the drivers I've found with "NI Instrument Driver Finder - Configure Search" I pops up with an error message saying
"Error -1073807195 occurred at VISA Open in Keithley 2000.lvlib:Initialize.vi->Keithley 2000 Read Multiple.vi?
Possible reason(s):
VISA: (Hex 0xBFFF00A5) The interface type is valid, but the specified interface number is not configured.?"
I've read all the threads I could find about this problem, but none of them helped. I've checked that the NiVi488.dll is checked in MAX under the VISA options. When I open the VISA Interactive Control I see an ASRL1>>ASRL1::INSTR and ASRL10>>ASRL10::INSTR. I don't know why it says ASRL, when I'm using an USB/GPIB interface, but the Keithley 2000 have 10 as the address. (the Agilent U2722A is connected directly by USB)
Assume I know nothing.
Thanks

I'm using the GPIB-USB-HS. I also used this on the development PC when I exported the hardware configuration.
This shows up in my MAX config and when I scan instruments, all of them show up. I can query them in MAX no problem.
My installer includes all the .exe's from my project. As I said, I've done this with my previous 2009 installer without any issue. I upgraded my installer since I upgraded my project for version 2013. The error only happens when I run my code.

Could not convert from java interface to interface type wsdl ??

i have a problem wheni have a problem when i develop bpel using mediator and wire to ejb service. When the mediator wire to ejb service, i found the error : Could not convert from java interface to interface type wsdl.... How to solve the problem?

I followed the case closely (with the same name of classes, methods, etc), but still get the error: “Could not convert from java interface to interface type wsdl.Exception=nl.amis.calculator.Calculator”. I created a Java class to test the lookup and function correctly. However, when I try to wire a Mediator to this Reference, I run into an Interface Conversion Error. I’ve included the line javaInterface = “nl.amis.calculator.Calculator” in file composite.xml, but still get error. Could you help me?

SLD Application Programming Interface for ABAP-Based Systems

Hi Experts,
Could you help me to configure the connection between SLD ABAP API and the SLD manually?
Why we use SLD Application Programming Interface for ABAP-based systems (SLD ABAP API)?
please help.
Sushama

You have to use transaction SLDAPICUST in the business system to define the SLD access data. This data consists of the host and port of the SLD as well as a user and password (PIAPPLUSER, for example). You can use the entries that you maintained on your Integration Server.
The RFC destinations LCRSAPRFC and SAPSLDAPI are used for the SLD connection. They use the SLD access data maintained with transaction SLDAPICUST. The RFC destination LCRSAPRFC is used to read the exchange profile; SAPSLDAPI is used by the ABAP API.
The RFC destinations are also used to retrieve the information about where to retrieve the information about where to find the Integration Builder required for the proxy generation. This information is located in the exchange profile.
You have to create both RFC destinations in your business system. They use the same registered server program, which is defined as part of the RFC engine settings of the J2EE Engine on the Integration Server host. This means that all business systems can use the same server program for their RFC destinations LCRSAPRFC and SAPSLDAPI. This program ID is:
● SAPSLDAPI_UNICODE for Unicode business systems
● SAPSLDAPI_NONUNICODE
This should help

Outbound interface using ABAP Proxy

Hi Guys,
I am trying to create an interface between a Z table and XI using ABAP Proxy. I suggested file based interface, but client is insisting using ABAP proxy. Z table is in IS-Retail side.
I will appreciate is somebody can share a program to do this.
Any advise/guidance is appreciated.
Thanks,

Hi There
From your subject line i can see that you want to develop an outbound proxy which means you want to send data to XI from your SAP custom table. That means you need to extract all the information from your Z-table and send it to XI via proxy.
If my understanding is correct then what you need to do is :
1.Ask your XI team team to generate a message interface for you of type 'outbound' and include the structure in the way they want you to send data to them.
2.Once the message interface is created by them , you can generate the same in transaction SPROXY . Search for your interface namespace and then right click
on it and say 'CREATE' . Give the appropriate package and prefix to it.Generate the proxy, save and activate
3. Now you can create a report and then according to the structure generated by XI , you can popluate your internal table to be passed back.
4. Call the method of the proxy in your report and send the data to XI.
I can give you an example of how to do this:
suppose you have built up an internal table by extracting data from your Z-table .Lets say it is tbl_output.
In your report you need to trigger the proxy method as follows:
Note: i am assuming i am triggering an asynchronous proxy method from my report:
DATA:lo_senddata TYPE REF TO CL_DATA_OUT,
 lo_system_fault TYPE REF TO cx_ai_system_fault,
 lo_root TYPE REF TO cx_root.
ls_output-output_file-data[] = tbl_data[].
CREATE OBJECT lo_senddata
TRY.
* call the asynchronous method of the proxy and send the data
 CALL METHOD lo_senddata->execute_asynchronous
 EXPORTING
 output = ls_output.
* get the system exceptions and display the error text
 CATCH cx_ai_system_fault INTO lo_system_fault.
 WRITE:/ 'System Error:'(E01),
 lo_system_fault->errortext.
 RETURN.
* get the root exception and display the textid value
 CATCH cx_root INTO lo_root.
 WRITE:/ 'System Error:'(E01),
 lo_root->textid.
 RETURN.
 ENDTRY.
COMMIT WORK.
Note: 1. CL_DATA_OUT is the message interface class.
 2. ls_output is the output structure to be sent back to XI and data
 is an internal table with the same structure as tbl_data.
 3. It is very imp to catch exceptions as i have shown u above.
Please let me know if you are a little clear or you need some more clarifications on this.
cheers
shivika

Interfaces in ABAP

Can any one tell me how to handle interfaces in ABAP.
i would like to know what r all methodology or technology we can use like RFC,IDOC,BAPI,ALE,BDC.
Thanks in advance

HI ,
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
 The first is when application data to be replaced is transferred at once, and only once.
 The second situation is to transfer data periodically from external systems to SAP and vice versa.
 There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
 To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
 To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
 The transaction code, if you do not already know it.
 Which fields require input i.e., mandatory.
 Which fields can you allow to default to standard values.
 The names, types, and lengths of the fields that are used by a transaction.
 Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
 Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
 Step through the transaction, entering the data will be required for processing your batch input data.
 On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
 Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
 For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
 Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
 Create a BDCDATA structure
 Write the structure out to a session or process it with CALL TRANSACTION USING; and then
 Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
 Data that is entered into screen fields.
 Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
 PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
 DYNPRO: Screen Number. Set this field only in the first record for the screen.
 DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
 FNAM: Field Name. The FNAM field is not case-sensitive.
 FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
 User Name: User name
 Group: Name of the session
 Lock Date: The date on which you want to process the session.
 Keep: This parameter is passed as X when you want to retain session after
 processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
 Tcode: Transaction Name
 Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
 Mode <A/N/E>
 Update <S/A>
 Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
 A is all screen mode. All the screen of transaction are displayed.
 N is no screen mode. No screen is displayed when you execute the transaction.
 E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
 S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
 A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
 1. Tcode: Transaction code
 2. Dyname: Batch point module name
 3. Dynumb: Batch input Dyn number
 4. Msgtyp: Batch input message type (A/E/W/I/S)
 5. Msgspra: Batch input Lang, id of message
 6. Msgid: Message id
 7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
 Mode <A/N/E>
 Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
 SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
 (Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
 Mode <A/N/E>
 Update <S/A>
 Messages <BDCMSG>.
 Perform check.
 Refresh BDCTAB.
 Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
Check these links to know more
BAPI
http://www.allsaplinks.com/bapi.html
IDOC
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
Regards,
Santosh

Unable to create XML based interface while using Interactiveform UIelement

Dear All,
I have a node under a subnode which is of a structure type.
This structure has three components each of which is assigned a table type.
While generating the XML based interface, message 'unsupported types wont be generated' comes and in the following From layout, I find the data entries for this particular node are invisible.
Can you suggest a way to achieve the functionality?
Thank You.
Regards,
Prosenjit.

We should use only data elements and ABAP table structures while working with XML interfaces.

Payable Open Interface Import---Asset Book name is being generated

Hi,
I am working on Payables Open Interface Import in R12.
I am not generating the 'Track as Asset Flag' and 'Asset Book Type Code' fields in Ap_invoice_lines_nterface table.
And the distribution account is also an Expense account.
But after the payables open interface import is completed, the asset book name is being populated in ap_invoice_lines_all table.
and as a result, recoverable and non recoverable tax lines are being created in the ap_invoice_distributions_all table making the invoice total and line total unequal.
Did any body faced a similar issue?
Please help....
this is really very urgent.
Any queries, please ask me [email protected]
Thanks in advance,
Sharmila

Hi,
I have raised a SR with Oracle and got following suggestion:
=== ODM Solution /Action Plan ===
To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for Patch.9577089:R12.AP.B.
2. Ensure that you have taken a backup of your system before applying
the recommended patch.
3. Apply the patch in a test environment.
4. Confirm the following file versions:
120.67.12010000.27 of apiimutb.pls
You can use the commands like the following:
strings -a $XX_TOP/filename |grep '$Header'
5. Retest the issue.
6. Migrate the solution as appropriate to other environments.
Will keep you all posted.
Regards,
Sharmila

Interface Type "ABAP Dictionary-Based Interface" not generating Interac

Similar Messages

Maybe you are looking for