Read data from Inbound ABAP proxy.Experts.

Hi Experts,
I want to read data from a inbound proxy.
Data is inside a deep structure as input.
Inside that 6 fields are there , out of those 6 i am able to read data from 5 fildes which are of type string 1 field QUANT is there which is of "Proxy Table Type (generated)" having data type as string.
Now whenever i tried to assign this to any field or variable of type string or char it gives error as "can not be converted to type of" that quant field.
Please help thanks in advance.

Similar Messages

Reading Data from a Table With an Expert

Hi all - I'm trying to write an Expert in OWB that would read data from a table and create a new table based on that information. I have the table creation part down, but how can I read data from a table with an Expert? From what I've read, Experts only deal with metadata, and there is no mechanism in Experts to actually read data in the tables. Does OraTcl work in Experts? Has anyone ever came across this problem, and if so, how did you solve it? Thanks in advance for your time! - Don

Hi Don
Can also use Java and JDBC from within Tcl, see the routines in this file below, take modify or whatever;
http://blogs.oracle.com/warehousebuilder/ombora.tcl
source <dir>\ombora.tcl
set g_user scott
set g_upwd zzzzzz
set g_hostname localhost
set g_port 1521
set g_srvname ora111
oraconnect $g_user $g_upwd $g_hostname:$g_port:$g_srvname
oraselect "select * from emp" ""
As well as dumping the results to stdout (you probably want to comment that part out and change any other part you don't like), g_res is a ResultSet object you can use to do whatever.
Cheers
David

Hi experts, how to use open sql to read data from one " maintenance view"?

i want to use this part of data within report ,so how to use open sql statement to read data from one " maintenance view"?

Hi
You can't use OPEN SQl statements to fetch data from maintenance view
You have to use only Database views
see the different types of views and the difference
The followings are different types of views:
- Database View (SE11)
Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.
In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys.
- Help View ( SE54)
Help views are used to output additional information when the online help system is called.
When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.
- Projection View
Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed.
A projection view can draw upon only one table. Selection conditions cannot be specified for projection views.
- Maintenance View ( SE54 )
Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.
Please have a look at below link. It will help you.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
for more detailed info look on:
http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
Reward points for useful Answers
Regards
Anji

Read data from SharePoint using ABAP sql command

We need to read data from a SharePoint site and update the sap object services with the information. There is a lot of information on how to put data into Sharepoint from SAP, but we need to get data from SharePoint and put it into SAP. Is it possible to retrieve data from SharePoint using sql command in ABAP program? If it is possible, what do we need to do to have SAP recognize where to get the SharePoint data?
Richard Newman

Hi Newman,
You can use native sql in your abap code to read data from SharePoint's database. But I would suggest you to generate a SharePoint webservice which can provide you the neccessary data so that you can consume this webservice in ABAP
(Will be quite faster than native sql).
Regards,
Ozcan.

Read data from MDM For Lookup and Flat table using MDM ABAP API

Hi,
I have requriment to read data from MDM from FLAT and Lookup table using MDM ABAP API. My design is like this ,
I have one ITEMS (Main table in MDM) and inside that i have one Lookup flat table ITEM_TYPE , my requriment is to read Item number and its related Item type.
From ABAP.
Please help if any body has any idea.
Regards,
Shyam

HI Guys,
I found my solution by myself. Below is the solution , hope this will help others:-
Retrieve data from MDM using MDM ABAP API.
Step- 1. Create structure in SAP with the same name as that of MDM field code for MDM Main table.
Step-2. Create another structure in SAP having all lookup fields of MDM , fieldname in ECC must be same as that of MDM field
code.
Step-3.Create structure in SAP for individual lookup field(Single Field only) with the same name as MDM Field code.
Step-4.
DATA: IT_QUERY TYPE STANDARD TABLE OF MDM_QUERY, "MDM_QUERY_TABLE,
 WA_QUERY TYPE MDM_QUERY,
 WA_CDT_TEXT TYPE MDM_CDT_TEXT,
 IT_RESULT_SET_KEY TYPE MDM_SEARCH_RESULT_TABLE,
 WA_RESULT_SET_KEY TYPE MDM_SEARCH_RESULT,
 WA_STRING TYPE STRING.
DATA:<Internal table> TYPE STANDARD TABLE OF <SAP Str Having all LOOKup Fields>
DATA: :<Internal table>TYPE STANDARD TABLE OF <SAP Str one LOOKup field>,
 <Workarea> LIKE LINE OF :<Internal table>.
*PASS LOGICAL OBJECT NAME.
V_LOG_OBJECT_NAME = 'Logical object name defined in Customization'.
Define logon language, country & region for server
WA_LANGUAGE-LANGUAGE = 'eng'.
WA_LANGUAGE-COUNTRY = 'US'.
WA_LANGUAGE-REGION = 'USA'.
TRY.
 CREATE OBJECT LR_API
 EXPORTING
 IV_LOG_OBJECT_NAME = V_LOG_OBJECT_NAME.
ENDTRY.
CONNECT to repository. Apply particular logon language info
CALL METHOD LR_API->MO_ACCESSOR->CONNECT
EXPORTING
 IS_REPOSITORY_LANGUAGE = WA_LANGUAGE.
*NOW PASS ITEM NO AND GET KEY FROM MDM.
CLEAR WA_QUERY.
WA_QUERY-PARAMETER_CODE = <MDM FIELD CODE>. "Field code
WA_QUERY-OPERATOR = 'EQ'. "Contains
WA_QUERY-DIMENSION_TYPE = 1. "Field search
WA_QUERY-CONSTRAINT_TYPE = 8. "Text search
WA_STRING = <Field Value>.
GET REFERENCE OF WA_STRING INTO WA_QUERY-VALUE_LOW.
APPEND WA_QUERY TO IT_QUERY.
CLEAR WA_QUERY.
*PASS ITEM NUMBER AND GET RELATED KEY FROM MDM.
TRY.
 CALL METHOD LR_API->MO_CORE_SERVICE->QUERY
 EXPORTING
 IV_OBJECT_TYPE_CODE = <MDM Main Table>
 IT_QUERY = IT_QUERY
 IMPORTING
 ET_RESULT_SET = IT_RESULT_SET_KEY.
CATCH CX_MDM_COMMUNICATION_FAILURE .
CATCH CX_MDM_KERNEL .
CATCH CX_MDM_NOT_SUPPORTED .
CATCH CX_MDM_USAGE_ERROR .
CATCH CX_MDM_PROVIDER .
CATCH CX_MDM_SERVER_RC_CODE .
ENDTRY.
Pass record id into keys.
LOOP AT IT_RESULT_SET_KEY INTO WA_RESULT_SET_KEY.
WA_KEYS = WA_RESULT_SET_KEY-RECORD_IDS.
ENDLOOP.
WA_RESULT_SET_DEFINITION-FIELD_NAME = <Look field name>.
APPEND WA_RESULT_SET_DEFINITION TO IT_RESULT_SET_DEFINITION.
CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE
EXPORTING
 IV_OBJECT_TYPE_CODE = <MDM Main Table>
 IT_RESULT_SET_DEFINITION = IT_RESULT_SET_DEFINITION
 IT_KEYS = WA_KEYS
IMPORTING
 ET_RESULT_SET = IT_RESULT_SET.
LOOP AT IT_RESULT_SET INTO
 WA_RESULT_SET.
*PASS KEYS INTO MAIN TABLE TO GET Structure for FALT or Look up Table
TRY.
 CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
 EXPORTING
 IV_OBJECT_TYPE_CODE = <MDM Main Table>
 IT_KEYS = WA_KEYS
 IMPORTING
 ET_DDIC_STRUCTURE =<SAP Strct having all Look up fileds of MDM>
ENDTRY.
LOOP AT <SAP Strct having all Look up fileds of MDM> INTO <Work area>.
 CLEAR WA_KEYS.
 APPEND <Work area>-field name TO WA_KEYS.
 CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
 EXPORTING
 IV_OBJECT_TYPE_CODE = <MDM Lookup table name>
 IT_KEYS = WA_KEYS
 IMPORTING
 ET_DDIC_STRUCTURE = <Single Structure in SAP For Lookup field>.
 READ TABLE <Single Structure in SAP For Lookup field>. INTO <Work Area> INDEX 1.
Here you can get the value of realted lookup fields associated with main table data.
ENDLOOP.
ENDLOOP.
LR_API->MO_ACCESSOR->DISCONNECT( ).
Edited by: Shyam Babu Sah on Nov 24, 2009 4:52 AM

Read Data From DSO - In ABAP Program

HI Friends,
Can any one tell how to read Data from a DSO in a Abap Program on BI System itself......
Which is the better way to read data from DSO in Abap Program... Is it
1. Reading Data Directly From the Active Table Of the DSO ... or
2. Reading Data From DSO....
In case of reading data from DSO.... Which function module is used to do this work....When i searched the forum i came across 2 function Modules.... BAPI_ODSO_READ_DATA_UC and RSDRI_INFOPROV_READ..... Please let me know which one should be used....
Regards,
Shyam.

Hi Shyam,
The active content of any ods will be stored in the database tables( SE11) with the naming convention /BIC/A<odsname>00 for Custom-defined DSO and /BI0/A<odsname>00 for Business content delivered DSO.
For example if the technical name of the ods is TEST , then the active content table name in SE11 will be /BIC/ATEST00.
You can write your own program to read the contents of this database table.
Regards,
Krishna.

Problem with Inbound Abap Proxy

Hi Experts,
I have an Inbound ABAP proxy scenario that insert data into a ztable. The whole process from XI to R/3 works fine, except it does not update my ztable.
The only time the ztable gets updated is when i debug it. I used this report "SPRX_TEST_INBOUND" to debug
Anyone who's had a similar problem.
Thank you in Advance,
Danny

Hi,
did you use the same XML from SXMB_MONI that gets posted during message flow?
you can check inside your inbound proxy if the values are not empty etc
and then raise an exception to see what's going on
you can also do an endless loop and get inside it to see the real values
that get passed into the proxy
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Inbound ABAP Proxy

Hi All,
I have an inbound ABAP proxy as the receiver. The class, interface, structure and tables are generated when I created the proxy.
I edited the method execute_asynchronous to collect the data from the table and send it to another RFC.
When I tried to populate my internal table using the data from table generated during proxy generation, it gives me an error like"zjssrc_dt-header_tab" is not defined in the ABAP dictionary as table, projection view or database view. But it doesn't give me an error while declaring my internal table of the type "zjssrc_dt-header_tab".
Any inputs on this will be of great help.
Thanks & Regards,
Jai Shankar.

Hi,
When you generate your Proxy, there will be some structures created. Here you can see the name of the table type.
Just create a work are for the same table type and one internal table.
eg.
DATA: i_data_records TYPE TABLE OF zback_dt_data_records.
DATA: wa_data_records TYPE zback_dt_data_records.
Now move the data from the proxy to your internal table
eg.
i_data_records = input-mt_val_in-data_records.
Now this value input-mt_val_in-data_records for you would be input_<MessageType>_<segmentName thats repeating>
Now loop through the Internal table and move the data to Work area and then update your table.
I have taken second weblog as eg. Just see that weblog and read this.
Regards
Vijaya
Message was edited by: vijaya kumari

Debugging of inbound ABAP proxy

Please To show the debugging of inbound ABAP proxy, the implementation of the demo scenario is used. The demo scenario is available in any installation WebAS 6.40 or higher.

follow this method and check debugging mode.
Debugging of inbound proxies in WebAS 6.40 or higher
To show the debugging of inbound ABAP proxy, the implementation of the demo scenario is used. The demo scenario is available in any installation WebAS 6.40 or higher.
At first you have to set a break point in the ABAP code. Call transaction SPROXY. Expand the namespace http://sap.com/xi/XI/Demo/Airline, the node Message Interface (inbound) and the interface FlightBookingOrderRequest_In.
Double click on interface II_SXIDAL_FBO_REQUEST and get the view of the proxy object properties.
Double click on the implementing class (ABAP name) and then double click on the method name (this class has only one method).
Now you are in the inbound proxy implementation. Set the break point on the first executable line.
With help of the back button (F3) go back to the transaction SPROXY. Here you choose from menu Proxy -> Test Interface
In the next pop up check the field XML Editor to maintain the payload.
In the next screen apply suitable values or upload the XML payload of the SXMB_MONI (after mapping).
Now the inbound proxy processing should stop at the break point.
If the processing does not stop at the break point, there might be an error in the XML. Check at the result page for error messages.
Debugging of inbound proxies in WebAS 6.20
You set the break point the same way as described above.
To start the proxy test you call the report SPRX_TEST_INBOUND.
As parameters you enter the name of the ABAP interface and the method name of of the ABAP interface and check the parameter Edit Native XML
In the next screen you apply suitable values or upload the XML payload of the SXMB_MONI (after mapping).
Then you click first on save button (F11), then on back button (F3).
Now you should see your debug session. If not, check if the XML is valid. BAPI_GOODSMVT_CREATE to post Goods Movement
The following is an abap program making used of the BAPI function BAPI_GOODSMVT_CREATE to do Goods Receipts for Purchase Order after importing the data from an external system.
BAPI TO Upload Inventory Data
GMCODE Table T158G - 01 - MB01 - Goods Receipts for Purchase Order
 02 - MB31 - Goods Receipts for Prod Order
 03 - MB1A - Goods Issue
 04 - MB1B - Transfer Posting
 05 - MB1C - Enter Other Goods Receipt
 06 - MB11
Domain: KZBEW - Movement Indicator
 Goods movement w/o reference
B - Goods movement for purchase order
F - Goods movement for production order
L - Goods movement for delivery note
K - Goods movement for kanban requirement (WM - internal only)
O - Subsequent adjustment of "material-provided" consumption
W - Subsequent adjustment of proportion/product unit material
report zbapi_goodsmovement.
parameters: p-file like rlgrap-filename default
 'c:\sapdata\TEST.txt'.
parameters: e-file like rlgrap-filename default
 'c:\sapdata\gdsmvterror.txt'.
parameters: xpost like sy-datum default sy-datum.
data: begin of gmhead.
 include structure bapi2017_gm_head_01.
data: end of gmhead.
data: begin of gmcode.
 include structure bapi2017_gm_code.
data: end of gmcode.
data: begin of mthead.
 include structure bapi2017_gm_head_ret.
data: end of mthead.
data: begin of itab occurs 100.
 include structure bapi2017_gm_item_create.
data: end of itab.
data: begin of errmsg occurs 10.
 include structure bapiret2.
data: end of errmsg.
data: wmenge like iseg-menge,
 errflag.
data: begin of pcitab occurs 100,
 ext_doc(10), "External Document Number
 mvt_type(3), "Movement Type
 doc_date(8), "Document Date
 post_date(8), "Posting Date
 plant(4), "Plant
 material(18), "Material Number
 qty(13), "Quantity
 recv_loc(4), "Receiving Location
 issue_loc(4), "Issuing Location
 pur_doc(10), "Purchase Document No
 po_item(3), "Purchase Document Item No
 del_no(10), "Delivery Purchase Order Number
 del_item(3), "Delivery Item
 prod_doc(10), "Production Document No
 scrap_reason(10), "Scrap Reason
 upd_sta(1), "Update Status
 end of pcitab.
call function 'WS_UPLOAD'
exporting
 filename = p-file
 filetype = 'DAT'
IMPORTING
FILELENGTH =
tables
 data_tab = pcitab
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
OTHERS = 6
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
exit.
endif.
gmhead-pstng_date = sy-datum.
gmhead-doc_date = sy-datum.
gmhead-pr_uname = sy-uname.
gmcode-gm_code = '01'. "01 - MB01 - Goods Receipts for Purchase Order
loop at pcitab.
itab-move_type = pcitab-mvt_type.
itab-mvt_ind = 'B'.
itab-plant = pcitab-plant.
itab-material = pcitab-material.
itab-entry_qnt = pcitab-qty.
itab-move_stloc = pcitab-recv_loc.
itab-stge_loc = pcitab-issue_loc.
itab-po_number = pcitab-pur_doc.
itab-po_item = pcitab-po_item.
concatenate pcitab-del_no pcitab-del_item into itab-item_text.
itab-move_reas = pcitab-scrap_reason.
append itab.
endloop.
loop at itab.
write:/ itab-material, itab-plant, itab-stge_loc,
 itab-move_type, itab-entry_qnt, itab-entry_uom,
 itab-entry_uom_iso, itab-po_number, itab-po_item,
 pcitab-ext_doc.
endloop.
call function 'BAPI_GOODSMVT_CREATE'
exporting
 goodsmvt_header = gmhead
 goodsmvt_code = gmcode
TESTRUN = ' '
IMPORTING
 goodsmvt_headret = mthead
MATERIALDOCUMENT =
MATDOCUMENTYEAR =
tables
 goodsmvt_item = itab
GOODSMVT_SERIALNUMBER =
 return = errmsg
clear errflag.
loop at errmsg.
if errmsg-type eq 'E'.
 write:/'Error in function', errmsg-message.
 errflag = 'X'.
else.
 write:/ errmsg-message.
endif.
endloop.
if errflag is initial.
commit work and wait.
if sy-subrc ne 0.
 write:/ 'Error in updating'.
 exit.
else.
 write:/ mthead-mat_doc, mthead-doc_year.
 perform upd_sta.
endif.
endif.
 FORM UPD_STA *
form upd_sta.
loop at pcitab.
 pcitab-upd_sta = 'X'.
 modify pcitab.
endloop.
call function 'WS_DOWNLOAD'
 exporting
 filename = p-file
 filetype = 'DAT'
IMPORTING
FILELENGTH =
 tables
 data_tab = pcitab
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
OTHERS = 6
endform.
*--- End of Program
Finding the user-exits of a SAP transaction code
Finding the user-exits of a SAP transaction code
Enter the transaction code in which you are looking for the user-exit
and it will list you the list of user-exits in the transaction code.
Also a drill down is possible which will help you to branch to SMOD.
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
 tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
 select single * from tadir where pgmid = 'R3TR'
 and object = 'PROG'
 and obj_name = tstc-pgmna.
 move : tadir-devclass to v_devclass.
 if sy-subrc ne 0.
 select single * from trdir where name = tstc-pgmna.
 if trdir-subc eq 'F'.
 select single * from tfdir where pname = tstc-pgmna.
 select single * from enlfdir where funcname =
 tfdir-funcname.
 select single * from tadir where pgmid = 'R3TR'
 and object = 'FUGR'
 and obj_name eq enlfdir-area.
 move : tadir-devclass to v_devclass.
 endif.
 endif.
 select * from tadir into table jtab
 where pgmid = 'R3TR'
 and object = 'SMOD'
 and devclass = v_devclass.
 select single * from tstct where sprsl eq sy-langu and
 tcode eq p_tcode.
 format color col_positive intensified off.
 write:/(19) 'Transaction Code - ',
 20(20) p_tcode,
 45(50) tstct-ttext.
 skip.
 if not jtab[] is initial.
 write:/(95) sy-uline.
 format color col_heading intensified on.
 write:/1 sy-vline,
 2 'Exit Name',
 21 sy-vline ,
 22 'Description',
 95 sy-vline.
 write:/(95) sy-uline.
 loop at jtab.
 select single * from modsapt
 where sprsl = sy-langu and
 name = jtab-obj_name.
 format color col_normal intensified off.
 write:/1 sy-vline,
 2 jtab-obj_name hotspot on,
 21 sy-vline ,
 22 modsapt-modtext,
 95 sy-vline.
 endloop.
 write:/(95) sy-uline.
 describe table jtab.
 skip.
 format color col_total intensified on.
 write:/ 'No of Exits:' , sy-tfill.
 else.
 format color col_negative intensified on.
 write:/(95) 'No User Exit exists'.
 endif.
 else.
 format color col_negative intensified on.
 write:/(95) 'Transaction Code Does Not Exist'.
 endif.
at line-selection.
 get cursor field field1.
 check field1(4) eq 'JTAB'.
 set parameter id 'MON' field sy-lisel+1(10).
 call transaction 'SMOD' and skip first screen.
*---End of Program
u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026
Difference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
 i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
 Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
 ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
 Ex:- 'Development server'>'Quality server'-> 'Production server'......
List Of User Exit Related to VL01N
I need to some restriction in fields ( Actual GI Date, T-Code:Vl01n ).
How do you find out whcih user exits belongs to VL01n ?
Here is the list of user exit related to VL01N :
V02V0001 - Sales area determination for stock transport order
V02V0002 - User exit for storage location determination
V02V0003 - User exit for gate + matl staging area determination
V02V0004 - User Exit for Staging Area Determination (Item)
V50PSTAT - Delivery: Item Status Calculation
V50Q0001 - Delivery Monitor: User Exits for Filling Display Fields
V50R0001 - Collective processing for delivery creation
V50R0002 - Collective processing for delivery creation
V50R0004 - Calculation of Stock for POs for Shipping Due Date List
V50S0001 - User Exits for Delivery Processing
V53C0001 - Rough workload calculation in time per item
V53C0002 - W&S: RWE enhancement - shipping material type/time slot
V53W0001 - User exits for creating picking waves
VMDE0001 - Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 - Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 - Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 - Shipping Interface: Message SDPACK (Packing, Inbound)

Inbound ABAP proxy in batch mode

Hi,
Is it possible to post the message to target SAP system using inbound abap proxy in batch mode instead of default dialog mode ? If anyone has done this, can you please let me know how to do it.
Thanks
Shany

Any comments from PI experts on this ?

How to read data from an internal table into a real table?

Hello experts,
I'm relatively new to ABAP and I'm trying to figure out how to read data from an internal table into a table that I created. I'm trying to use the RRW3_GET_QUERY_VIEW_DATA function module to read data from a multiprovider. I'm trying to read data from the e_cell_data and e_axis_data tables into a table that I've already created. Please see code below.
TABLES MULTITAB.
DATA:
query_name TYPE RSZCOMPID,
s_cubename TYPE RSINFOPROV,
t_cell_data TYPE RRWS_T_CELL,
t_axis_data TYPE RRWS_THX_AXIS_DATA,
t_axis_info TYPE RRWS_THX_AXIS_INFO,
wa_t_cell_data like line of t_cell_data,
wa_t_axis_data like line of t_axis_data,
w_corp_tab like line of t_cell_data.
s_cubename = 'CORP_MPO1'.
query_name = 'Z_corp_test'.
 CALL FUNCTION 'RRW3_GET_QUERY_VIEW_DATA'
 EXPORTING
 i_infoprovider = s_cubename
 i_query = query_name
 i_t_parameter = query_string_tab
 IMPORTING
 e_cell_data = t_cell_data
 e_axis_data = t_axis_data
 e_axis_info = t_axis_info.
If anyone has any information to help me, I would greatly appreciate it. Thanks.

Hi,
<li>Once you call the function module RRW3_GET_QUERY_VIEW_DATA, lets say data is available in the corresponding tables e_cell_data e_axis_data which you have mentioned.
<li>Modify your internal table defined for other purpose, with data from e_cell_data e_axis_data like below.
LOOP AT t_cell_data INTO wa_t_cell_data.
"Get the required data from t_cell_data.
MOVE-CORRESPONDING wa_t_cell_data TO it_ur_tab.
"Modify your internal table wih data
MODIFY it_ur_tab TRANSPORTING <field1> <field2> <field3>.
ENDLOOP.
LOOP AT t_axis_data INTO wa_t_axis_data.
"Get the required data from t_cell_data.
MOVE-CORRESPONDING wa_t_axis_data TO it_ur_tab.
"Modify your internal table wih data
MODIFY it_ur_tab TRANSPORTING <field1> <field2> <field3>.
ENDLOOP.
Thanks
Venkat.O

Unable to read data from the SAP Service Marketplace issue

Good morning, experts.
I´ve just installed the SAP Download Manager, but I can´t get connected to Marketplace.
First I tried downloading a file I could see in my Basket Download. Then I deleted it from the basket so I could test only the connection. In both situations I got the same error message: "Unable to read data from the SAP Service Marketplace (...)".
It is probably due to wrong settings, but I can´t figure it out. My settings are:
Address: https://websmp205.sap-ag.de/
User name: S0005951541
Password: (my password)
Proxy (my proxy settings)
Any ideas?

Thanks for your answer.
I can see my download basket online. I realize I didn´t delete the items so I could test purely the connection. I am going to do it again.
I found out I dind´t have permission to download those items, and with the right permission I could download them directly online.
As long as I have more information I am going to repost this issue on a new forum.
Thanks.

Issue with inbound abap proxy

I have an Inbound ABAP proxy scenario , the ABAP code inserts data into a ZTable.
I am having an issue in the runtime where
1. I see transaction data in SXI_MONITOR of both XI & application system.
2. if tried to debug with the report SPRX_TEST_INBOUND (as the application system WebAS is 6.20) the proxy code works just fine, and records are inserted in the ZTable.
records are not getting inserted into the table when run end to end..anybody faced this situation ?
Appreciate genuine replies....

Hi,
but this just has to work
if this doesn't work then "something realy strange is going around here"
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Inbound ABAP proxy in the IS localhost

Hello, Is there anyone who knows what I need to do to create an Inbound ABAP Proxy that execute a method in the Integration Server localhost.
regards
Ernesto Duran

Hello the reason is that I want to split a message I receive from the jdbc adapter. Anyway in webMethods you can always manipulate your XML messages and then resend them to a broker(wM Broker) or a publish/subscriber system (wM TN) and trigger a new process. In XI I only see the posbility to pass document from one system to another. Maybe the point is to work in another way that I still don't understand. Please look at my topic "JDBC adapter and message split" to get more information about my problem.

Where we should implement inbound abap proxy?

I have to implement Inbound abap proxy, there i need to call two BAPI s to create reservation and purchase requisition based on material number coming from input.
my doubt is all this code where should i implement and also please give me some sample codes.
Thank you
Neelima

Hi,
U can find the code in the following link,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/06adbf03-0a01-0010-f386-d8e45561a3c4
ABAP Inbound Proxy Error !
Problem with Inbound Abap Proxy
How to call BAPI from ABAP Inbound Proxy
issue with inbound abap proxy
Reward If Helpful,
Jagadish.

Read data from Inbound ABAP proxy.Experts.

Similar Messages

Maybe you are looking for