Parameters for calling PCR Direct Launch

Hi,
We have a custom webDynpro that lets manager select employees outside of their org unit for transfer into their org unit. Once the employee is selected how do we call the PCR Direct Launch iview with this employee number as a parameter? Is it even possible?
We are on ECC 6.0 and portal 7.0
thanks
Salim

Hello Salim,
i think i got it now what you are trying to achive. The positive thing is, there is an application called "PcrDirectLaunchApplication" which allows you to "skip" the employee-selection". The bad thing, you wont be able to easily pass the pernr via an URI parameter. Its a bit more complicated. I will have a look how to achive it. Will keep you posted
cheers,
Markus

Similar Messages

Disable G722 Advertisement for Call Recording/Monitoring

I'm troublshooting some call recording/monitoring issues and have come across many steps that reference disabling the "Advertise G.722 codec" in Enterprise Parameters for call manager.
Contact Center itself can only operate in G711 or G729 and I've validated when agents are on a call with their UCCX extension that they are using the G711 codec. Since UCCX cannot operate at G722 and my agents are taking calls are using G711, what is the reason why the G722 codec advertisement needs to be disabled?
Thanks.

Hi Paul,
It's not the G722 to UCCX that you need to worry about, because the IP Phone will negotiate G711 and not G722. Both parties have to support it in order for it to be used. An example of this is an IP Phone calling a UCCX trigger and interacting with a script.
However, it's the internal calls to Agents that you need to worry about. An example of this is an internal employee calling the Help Desk and speaking to an Agent. At this point, the two IP Phones will negotiate G722 and when the UCCX system tries to monitor or record that conversation, it cannot.
UCCX can only mon/rec G729 or G711. Therefore, if you didn't care about UCCX based mon/rec, then leave G722 enabled. It doesn't break your UCCX as a whole, it only prevents you from mon/rec those specific calls. Calls inbound from the PSTN would likely be G711, and would still work for mon/rec.
Does that make sense?
Anthony Holloway
Please use the star ratings to help drive great content to the top of searches.
EDIT: Added some more clarity.

URL to directly launch the Contribution console for a particular site

Looking for the URL that will directly launch the Webcenter Sites Contribution console for a particular site. Can we have such a URL (might be with site id and/or any other parameter) that will directly take us to that site when we launch http://<host>:<port>/cs/...?....
Thanks
Arijit

Understood. Good question. You certainly won't be the last one to ask that. The short version is "I don't know", but the longer version is that it's possible to figure it out.
The contributor UI is set up so that you can override any element you want. You're going to want to figure out which session variable is set to hold the site id - it's probably "pubid". Then, create a dedicated CSElement/SiteEntry pair that is the URL that you redirect to. Then element does nothing but pre-set pubid to what you want, and then calls the "front door" the UI. At that point, the framework should pick up the newly set pubid and you're off to the races.
Caveat - I haven't tried this on the contributor UI yet but it works beautifully on the advanced UI to do all sorts of things - like creating a URL directly to an asset's edit screen etc.
Good luck!

Visual Basic code genration for calling BAPI_SALESORDER_SIMULATE

Hi gurus,
Someone asked me how to generate the visual basic code for calling BAPI_SALESORDER_SIMULATE via RFC. I thought this function was available in SE37 but I can't find it...
Can someone help me ?
Thank you
Jean-Michel

**　プログラムＩＤ　　　　　　 ： ZBAPI_SALESORDER_CREATE *
**　プログラム名称　　 　　 ： Upload Sales Order Creation *
**　処理概要　　　　　　　 　： *
**　作成者　　　　　　　　　　 ： Karthik.P *
**　作成日　　　　　　　　　　 ： 2006/08/10 *
REPORT ZBAPI_SALESORDER_CREATE LINE-SIZE 132 MESSAGE-ID ZMMBAPI .
 Internal table definition *
****<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>>>
DATA: GT_ORDER_HEADER_IN LIKE BAPISDHD1,
*******<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
 GT_ORDER_HEADER_INX LIKE BAPISDHD1X,
*****<<<<<Return Parameter>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
 GT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE, " Return Messages
*********<<<Communication Fields: Sales and Distribution Document Item<>>>>>
 GT_ORDER_ITEMS_IN LIKE BAPISDITM OCCURS 0 WITH HEADER LINE, " Item Data
*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
 GT_ORDER_ITEMS_INX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE, "Item Data Checkbox
*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
 GT_SALESDOCUMENT LIKE BAPIVBELN-VBELN , "Number of Generated Document
*********<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
 GT_ORDER_PARTNERS LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE, "Document Partner
********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
 GT_ORDER_SCHEDULES_IN LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE, "Schedule Line Data
****<<<<<<<<Checkbox List for Maintaining Sales Document Schedule Line>>>>>>>>
 GT_ORDER_SCHEDULES_INX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE, " Checkbox Schedule Line Data
*******Communication Fields for Maintaining Conditions in the Order
 GT_ORDER_CONDITIONS_IN LIKE BAPICOND OCCURS 0 WITH HEADER LINE,
******Communication Fields for Maintaining Conditions in the Order
 GT_ORDER_CONDITIONS_INX LIKE BAPICONDX OCCURS 0 WITH HEADER LINE.
 Data definition *
DATA: BEGIN OF GT_FT_SALES OCCURS 0,
 DOC_TYPE(4) , "Sales Document Type
 SALES_ORG(4) , "Sales Organization
 DISTR_CHAN(2) , "Distribution Channel
 DIVISION(2) , "DIVISION(2)
 SALES_DIST(6) , "Sales district
 INCOTERMS1(3) , "Incoterms (part 1)
 INCOTERMS2(28) , "Incoterms (part 2)
 PMNTTRMS(4) , "Terms of payment key
 PRICE_DATE(8) , "Date for pricing and exchange rate
 PURCH_NO_C(35) , "Customer purchase order number
 PURCH_NO_S(35) , "Ship-to Party's Purchase Order Number
 EXCHG_RATE(8) , "Directly quoted exchange rate for pricing and statistics
 CURRENCY(5) , "SD document currency
 MATERIAL(18), "MATERIAL
 TARGET_QTY(13) , "Target quantity in sales units
 ITEM_CATEG(4) , "Sales document item category
 MATL_GROUP(8) , "Material Group
 PURCH_NO_C1(35), "Customer purchase order number
 SALES_DIST1(6) , "Sales district
 INCOTERMS11(3) , "Incoterms (part 1)
 INCOTERMS21(28), "Incoterms (part 2)
 PMNTTRMS1(4) , "Terms of payment key
 EXCHG_RATE1(8) , "Directly quoted exchange rate for pricing and statistics
 PRICE_DATE1(8) , "Date for pricing and exchange rate
 TRG_QTY_NO(5) , "Factor for converting sales units to base units (target qty)
 DIVISION1(2) , "DIVISION1
 SALQTYNUM(5) , "Numerator (factor) for conversion of sales quantity into SKU
 GROSS_WGHT(3) , "Gross Weight of the Item
 NET_WEIGHT(15) , "Net Weight of the Item
 UNTOF_WGHT(3) ,"Weight Unit
 PARTN_ROLE(2) ,"Partner function
 PARTN_NUMB(10) ,"Customer Number 1
********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
 ITM_NUMBER(6) ,"Item number of the SD document
 REQ_QTY(8) , "Schedule line date
 DLV_DATE(8) , "Schedule line date
 MS_DATE(8) , "Material availability date
 LOAD_DATE(8) , "Loading time (local time with reference to a shipping point)
 GI_DATE(8), "Time of goods issue (local DATE, with reference to a plant)
 TP_DATE(8) , "Transportation planning -time (local w/ref. to shipping pnt)
 ITM_NUMBER2(6) , "Condition item number
END OF GT_FT_SALES,
 MSG(240) TYPE C, " Return Message
 E_REC(8) TYPE C, " Error Records Counter
 REC_NO(8) TYPE C, " Records Number Indicator
 S_REC(8) TYPE C, " Successful Records Counter
 T_REC(8) TYPE C. " Total Records Counter
selection block for EXCEL UPLOAD FILE>>>>>>>>>>>>>>>>>>>>>>>>
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETERS FILE TYPE IBIPPARMS-PATH OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B1.
*<<<<AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .>>>>>>>>>>>>
AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
 IMPORTING
 FILE_NAME = FILE.
**<<<<<<<<<<<<<<<<<START-OF-SELECTION.>>>>>>>>>>>>>>>>>>>>>>>>>>>
START-OF-SELECTION.
CALL FUNCTION 'WS_UPLOAD' "#EC *
 EXPORTING
 FILENAME = FILE
 FILETYPE = 'DAT'
 TABLES
 DATA_TAB = GT_FT_SALES
 EXCEPTIONS
 CONVERSION_ERROR = 1
 FILE_OPEN_ERROR = 2
 FILE_READ_ERROR = 3
 INVALID_TYPE = 4
 NO_BATCH = 5
 UNKNOWN_ERROR = 6
 INVALID_TABLE_WIDTH = 7
 GUI_REFUSE_FILETRANSFER = 8
 CUSTOMER_ERROR = 9
 NO_AUTHORITY = 10
 OTHERS = 11.
IF SY-SUBRC <> 0 .
 MESSAGE E000.
ENDIF.
SKIP 3.
FORMAT COLOR COL_HEADING INVERSE ON.
 WRITE 40 TEXT-001.
FORMAT COLOR COL_HEADING INVERSE OFF.
SKIP 1.
FORMAT COLOR COL_NEGATIVE INVERSE ON.
 WRITE :/ TEXT-002, 13 SY-MANDT , 104 TEXT-003, 111 SY-UNAME,
 / TEXT-004, 13 SY-DATUM , 104 TEXT-005, 111 SY-UZEIT.
FORMAT COLOR COL_NEGATIVE INVERSE OFF.
SKIP 3.
LOOP AT GT_FT_SALES.
 PERFORM SLALE_UPLOAD_DATA.
ENDLOOP.
T_REC = E_REC + S_REC.
SKIP 3.
FORMAT COLOR COL_TOTAL INVERSE ON.
 WRITE: /38 TEXT-007, T_REC.
FORMAT COLOR COL_TOTAL INVERSE OFF.
FORMAT COLOR COL_NEGATIVE INVERSE ON.
 WRITE: /38 TEXT-008, E_REC.
FORMAT COLOR COL_NEGATIVE INVERSE OFF.
FORMAT COLOR COL_TOTAL INVERSE ON.
 WRITE: /38 TEXT-009, S_REC.
FORMAT COLOR COL_TOTAL INVERSE OFF.
*& Form SLALE_UPLOAD_DATA
 text
--> p1 text
<-- p2 text
FORM SLALE_UPLOAD_DATA .
*******<<<<<<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>
 GT_ORDER_HEADER_IN-DOC_TYPE = 'TA'.
 GT_ORDER_HEADER_IN-SALES_ORG = GT_FT_SALES-SALES_ORG . "'0001'
 GT_ORDER_HEADER_IN-DISTR_CHAN = GT_FT_SALES-DISTR_CHAN. "'01'
 GT_ORDER_HEADER_IN-DIVISION = GT_FT_SALES-DIVISION. " '01'
 GT_ORDER_HEADER_IN-SALES_DIST = GT_FT_SALES-SALES_DIST ."'000001'
 GT_ORDER_HEADER_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1. "'CFR'
 GT_ORDER_HEADER_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
 GT_ORDER_HEADER_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS . "'0001'
 GT_ORDER_HEADER_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE ."'20060818'
 GT_ORDER_HEADER_IN-PURCH_NO_C = '32'.
 GT_ORDER_HEADER_IN-PURCH_NO_S = '32'.
 GT_ORDER_HEADER_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE ."'1.00000'
 GT_ORDER_HEADER_IN-CURRENCY = GT_FT_SALES-CURRENCY . " 'EUR'
********<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
 GT_ORDER_HEADER_INX-DOC_TYPE = 'X'.
 GT_ORDER_HEADER_INX-SALES_ORG = 'X'.
 GT_ORDER_HEADER_INX-DISTR_CHAN = 'X'.
 GT_ORDER_HEADER_INX-DIVISION = 'X'.
 GT_ORDER_HEADER_INX-SALES_DIST = 'X'.
 GT_ORDER_HEADER_INX-INCOTERMS1 = 'X'.
 GT_ORDER_HEADER_INX-INCOTERMS2 = 'X'.
 GT_ORDER_HEADER_INX-PMNTTRMS = 'X'.
 GT_ORDER_HEADER_INX-PRICE_DATE = 'X'.
 GT_ORDER_HEADER_INX-PURCH_NO_C = 'X'.
 GT_ORDER_HEADER_INX-PURCH_NO_S = 'X'.
 GT_ORDER_HEADER_INX-EXCHG_RATE = 'X'.
 GT_ORDER_HEADER_INX-CURRENCY = 'X'.
*****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
 GT_ORDER_ITEMS_IN-ITM_NUMBER = '000010'.
 GT_ORDER_ITEMS_IN-MATERIAL = GT_FT_SALES-MATERIAL .
 GT_ORDER_ITEMS_IN-PO_ITM_NO = '32'.
 GT_ORDER_ITEMS_IN-CUST_MAT22 = 'AGNI-IV'.
 GT_ORDER_ITEMS_IN-BILL_DATE = '20060808'.
 GT_ORDER_ITEMS_IN-PLANT = '0001'.
*GT_ORDER_ITEMS_IN-STORE_LOC = '0001'.
 GT_ORDER_ITEMS_IN-TARGET_QTY = GT_FT_SALES-TARGET_QTY . "'1000'
 GT_ORDER_ITEMS_IN-ITEM_CATEG = GT_FT_SALES-ITEM_CATEG . "'TAN'
 GT_ORDER_ITEMS_IN-MATL_GROUP = GT_FT_SALES-MATL_GROUP . "'01'
 GT_ORDER_ITEMS_IN-PURCH_NO_C = GT_FT_SALES-PURCH_NO_C . "'32'
 GT_ORDER_ITEMS_IN-SALES_DIST = GT_FT_SALES-SALES_DIST . "'000001'
 GT_ORDER_ITEMS_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1 . "'CFR'
 GT_ORDER_ITEMS_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
 GT_ORDER_ITEMS_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS . "'0001'.
 GT_ORDER_ITEMS_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE . "'1.00000'
 GT_ORDER_ITEMS_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE . "'20060808'
*GT_ORDER_ITEMS_IN-SALES_UNIT = 'DZ'.
 GT_ORDER_ITEMS_IN-TRG_QTY_NO = GT_FT_SALES-TRG_QTY_NO . "'23'
 GT_ORDER_ITEMS_IN-DIVISION = GT_FT_SALES-DIVISION . "'01'
 GT_ORDER_ITEMS_IN-SALQTYNUM = GT_FT_SALES-SALQTYNUM . "'32'
 GT_ORDER_ITEMS_IN-GROSS_WGHT = GT_FT_SALES-GROSS_WGHT. " ' 25272000'
 GT_ORDER_ITEMS_IN-NET_WEIGHT = GT_FT_SALES-NET_WEIGHT. "'24464000'
 GT_ORDER_ITEMS_IN-UNTOF_WGHT = GT_FT_SALES-UNTOF_WGHT . " 'KG'
*GT_ORDER_ITEMS_IN-CURRENCY = 'EUR'.
 APPEND GT_ORDER_ITEMS_IN.
****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
 GT_ORDER_ITEMS_INX-ITM_NUMBER = '000010'.
 GT_ORDER_ITEMS_INX-MATERIAL = 'X'.
*GT_ORDER_ITEMS_INX-PO_ITM_NO = 'X'.
 GT_ORDER_ITEMS_INX-CUST_MAT22 = 'X'.
 GT_ORDER_ITEMS_INX-BILL_DATE = 'X'.
 GT_ORDER_ITEMS_INX-PLANT = 'X'.
*GT_ORDER_ITEMS_INX-STORE_LOC = 'X'.
 GT_ORDER_ITEMS_INX-TARGET_QTY = 'X'.
 GT_ORDER_ITEMS_INX-ITEM_CATEG = 'X'.
 GT_ORDER_ITEMS_INX-MATL_GROUP = 'X'.
 GT_ORDER_ITEMS_INX-PURCH_NO_C = 'X'.
 GT_ORDER_ITEMS_INX-SALES_DIST = 'X'.
 GT_ORDER_ITEMS_INX-INCOTERMS1 = 'X'.
 GT_ORDER_ITEMS_INX-INCOTERMS2 = 'X'.
 GT_ORDER_ITEMS_INX-PMNTTRMS = 'X'.
 GT_ORDER_ITEMS_INX-EXCHG_RATE = 'X'.
 GT_ORDER_ITEMS_INX-PRICE_DATE = 'X'.
*GT_ORDER_ITEMS_INX-SALES_UNIT = 'X'.
 GT_ORDER_ITEMS_INX-TRG_QTY_NO = 'X'.
 GT_ORDER_ITEMS_INX-DIVISION = 'X'.
 GT_ORDER_ITEMS_INX-SALQTYNUM = 'X'.
 GT_ORDER_ITEMS_INX-GROSS_WGHT = 'X'.
 GT_ORDER_ITEMS_INX-NET_WEIGHT = 'X'.
 GT_ORDER_ITEMS_INX-UNTOF_WGHT = 'X'.
*GT_ORDER_ITEMS_IN-CURRENCY = 'x'.
 APPEND GT_ORDER_ITEMS_INX.
*****<<<<<<Communications Fields: SD Document Partner: WWW
 GT_ORDER_PARTNERS-PARTN_ROLE = 'WE'.
 GT_ORDER_PARTNERS-PARTN_NUMB = '0000000057'.
***GT_ORDER_PARTNERS-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER . " '000010'.
 APPEND GT_ORDER_PARTNERS.
*********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
 GT_ORDER_SCHEDULES_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER." '000010'
 GT_ORDER_SCHEDULES_IN-REQ_QTY = GT_FT_SALES-REQ_QTY . "'234'
 GT_ORDER_SCHEDULES_IN-DLV_DATE = GT_FT_SALES-DLV_DATE ." '20060824'.
 GT_ORDER_SCHEDULES_IN-MS_DATE = GT_FT_SALES-MS_DATE . "'20060808'
 GT_ORDER_SCHEDULES_IN-LOAD_DATE = GT_FT_SALES-LOAD_DATE. " '20060822'
 GT_ORDER_SCHEDULES_IN-GI_DATE = GT_FT_SALES-GI_DATE . " '20060823'
 GT_ORDER_SCHEDULES_IN-TP_DATE = GT_FT_SALES-TP_DATE . "'20060821'
 APPEND gt_ORDER_SCHEDULES_IN.
*********<<<<Communications Fields: SD Document Partner: WWW FLAG>>>>>>>>>>>>>>>>>>
 GT_ORDER_SCHEDULES_INX-ITM_NUMBER = '000010'.
 GT_ORDER_SCHEDULES_INX-REQ_QTY = 'X'.
 GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
 GT_ORDER_SCHEDULES_INX-MS_DATE = 'X'.
 GT_ORDER_SCHEDULES_INX-LOAD_DATE = 'X'.
 GT_ORDER_SCHEDULES_INX-GI_DATE = 'X'.
 GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
 APPEND gt_ORDER_SCHEDULES_INX.
********Communication Fields for Maintaining Conditions in the Order
 GT_ORDER_CONDITIONS_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER ." '000010'
 APPEND GT_ORDER_CONDITIONS_IN.
***Communication Fields for Maintaining Conditions in the Order
 GT_ORDER_CONDITIONS_INX-ITM_NUMBER = '000010'.
 APPEND GT_ORDER_CONDITIONS_INX.
 CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
 EXPORTING
 SALESDOCUMENTIN =
 ORDER_HEADER_IN = GT_ORDER_HEADER_IN
 ORDER_HEADER_INX = GT_ORDER_HEADER_INX
SENDER =
BINARY_RELATIONSHIPTYPE =
INT_NUMBER_ASSIGNMENT =
BEHAVE_WHEN_ERROR =
LOGIC_SWITCH =
TESTRUN =
CONVERT = ' '
 IMPORTING
 SALESDOCUMENT = GT_SALESDOCUMENT
 TABLES
 RETURN = GT_RETURN
 ORDER_ITEMS_IN = GT_ORDER_ITEMS_IN
 ORDER_ITEMS_INX = GT_ORDER_ITEMS_INX
 ORDER_PARTNERS = GT_ORDER_PARTNERS
 ORDER_SCHEDULES_IN = GT_ORDER_SCHEDULES_IN
 ORDER_SCHEDULES_INX = GT_ORDER_SCHEDULES_INX
 ORDER_CONDITIONS_IN = GT_ORDER_CONDITIONS_IN
 ORDER_CONDITIONS_INX = GT_ORDER_CONDITIONS_INX
ORDER_CFGS_REF =
ORDER_CFGS_INST =
ORDER_CFGS_PART_OF =
ORDER_CFGS_VALUE =
ORDER_CFGS_BLOB =
ORDER_CFGS_VK =
ORDER_CFGS_REFINST =
ORDER_CCARD =
ORDER_TEXT =
ORDER_KEYS =
EXTENSIONIN =
PARTNERADDRESSES =
 IF GT_RETURN-TYPE EQ 'E' .
 E_REC = E_REC + 1.
 READ TABLE GT_RETURN WITH KEY ID = 'V1'.
 FORMAT COLOR COL_NEGATIVE INVERSE ON.
 REC_NO = E_REC + S_REC.
 CONCATENATE TEXT-006 REC_NO ':'
 GT_RETURN-MESSAGE INTO MSG SEPARATED BY SPACE .
 CONDENSE MSG.
 WRITE: / MSG.
 FORMAT COLOR COL_NEGATIVE INVERSE OFF.
ELSEIF GT_RETURN-TYPE EQ 'S'.
 S_REC = S_REC + 1.
 FORMAT COLOR COL_POSITIVE INVERSE ON.
 MSG = GT_RETURN-MESSAGE.
 CONDENSE MSG.
 WRITE: / MSG .
 FORMAT COLOR COL_POSITIVE INVERSE OFF.
 PERFORM COMMIT_MM.
ENDIF.
 CLEAR: GT_RETURN[], MSG.
ENDFORM. " SLALE_UPLOAD_DATA
*& Form COMMIT_MM
 text
--> p1 text
<-- p2 text
FORM COMMIT_MM .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 WAIT = 'X'
 IMPORTING
 RETURN = GT_RETURN.
clear: GT_ORDER_ITEMS_IN[],GT_ORDER_CONDITIONS_IN[].
ENDFORM. " COMMIT_MM

Adding custom Adapter information Parameters for Oracle Inbound Telephony

Hello,
I am implementing a custom adapter for Oracle Inbound telephony. I need to configure a few information parameters for my custom adapter. I am using the "Adapter Server Info <1-6>" fields on the Call Center html administration page (under the "Middleware" section). But I need to configure more than 6 parameters for my adapter. Does anyone know if we can add more "Adapter Server Info" fields?

You may explore using a BPEL process to set the so header for calling the web service instead of directly calling it from BPMN process.
Steps.
1)Create a BPEL process.
2)Select the checkbox "Expose as a SOAP service"
3)In the BPEL process, set the SOAP header parameters that are expected by the called web service.
Refer section
6.22.2 How to Send SOAP Headers in BPEL
of
Oracle® Fusion Middleware
Developer’s Guide for Oracle SOA Suite
11g Release 1 (11.1.1.6.3)
E10224-15
4)Now in your BPM web service adapter , instead of calling the web service directly, call the web service endpoint of the newly created BPEL process.
Hope this helps.
Regards.

How to log input parameters for Function Modules?

Hi,
I need to create a Logging system to trace input parameters for function modules.
The log functionality could be done by developing a class method or a function module (For example 'write_log'), and calling it within each function module that I want to log. The 'write_log' code should be independent from the interface of the Function Module that I want to log.
For example, I'd like to write a function/class method that can log both these functions modules:
Function DummyA
 Input parameters: A1 type char10, A2 type char10.
Function DummyB
 Input parameters: B1 type char20, B2 type char20, B3 type char20, B4 type Z_MYSTRUCTURE
Now the questions...
- Is there a "standard SAP" function that provide this functionality?
- If not, is there a system variable in which I can access runtime all parameters name, type and value for a particular function module?
- If not, how can I loop at Input parameters in a way that is independent from the function module interface?
Thank you in advance for helping!

check this sample code. here i am capturing only parameters (import) values. you can extend this to capture tables, changin, etc.
FUNCTION y_test_fm.
*"*"Local Interface:
*" IMPORTING
*" REFERENCE(PARAM1) TYPE CHAR10
*" REFERENCE(PARAM2) TYPE CHAR10
*" REFERENCE(PARAM3) TYPE CHAR10
DATA: ep TYPE STANDARD TABLE OF rsexp ,
 ip TYPE STANDARD TABLE OF rsimp ,
 tp TYPE STANDARD TABLE OF rstbl ,
 el TYPE STANDARD TABLE OF rsexc ,
 vals TYPE tihttpnvp ,
 wa_vals TYPE ihttpnvp ,
 wa_ip TYPE rsimp .
FIELD-SYMBOLS: <temp> TYPE ANY .
CALL FUNCTION 'FUNCTION_IMPORT_INTERFACE'
 EXPORTING
 funcname = 'Y_TEST_FM'
* INACTIVE_VERSION = ' '
* WITH_ENHANCEMENTS = 'X'
* IGNORE_SWITCHES = ' '
* IMPORTING
* GLOBAL_FLAG =
* REMOTE_CALL =
* UPDATE_TASK =
* EXCEPTION_CLASSES =
 TABLES
 exception_list = el
 export_parameter = ep
 import_parameter = ip
* CHANGING_PARAMETER =
 tables_parameter = tp
* P_DOCU =
* ENHA_EXP_PARAMETER =
* ENHA_IMP_PARAMETER =
* ENHA_CHA_PARAMETER =
* ENHA_TBL_PARAMETER =
* ENHA_DOCU =
 EXCEPTIONS
 error_message = 1
 function_not_found = 2
 invalid_name = 3
 OTHERS = 4
IF sy-subrc = 0.
 LOOP AT ip INTO wa_ip .
 MOVE: wa_ip-parameter TO wa_vals-name .
 ASSIGN (wa_vals-name) TO <temp> .
 IF <temp> IS ASSIGNED .
 wa_vals-value = <temp> .
 ENDIF .
 APPEND wa_vals TO vals .
 ENDLOOP .
ENDIF.
ENDFUNCTION.

IPHONE 4S incoming calls go directly to voice mail. This is a brand new replacement phone. Prior phone didn't have this problem

IPHONE 4S incoming calls go directly to voice mail. This is a brand new replacement phone. Prior phone didn't have this problem

Slide up from the bottom of your display to access the control panel.
Look for the button (should be at the top) that shows a crescent moon.
Tap that button. It should say "Do not Disturb: Off".
Then try it out and let us know if it worked.

How to differentiate which is exporting and importing parameters when calling dynamically using CL_ABAP_OBJECTDESCR

Hello All,
First of all sorry for posting the question in general abap queries, since somehow I am not able to post in ABAP objects discussions.
My requirement is
Step 1 : To get table name as input and dynamically derive all fields which is going to be passed as parameters for a method
I did this using cl_abap_typedescr class
Step 2: Then Pass the values into the relevant fields using below code
ptab_line-name = 'DATA_TAB'.
ptab_line-kind =
cl_abap_objectdescr=>changing.
GET REFERENCE OF text_tab INTO
ptab_line-value.
INSERT ptab_line INTO TABLE ptab.
Step 3: Later I am calling dynamic class like
    CALL METHOD (class)=>(meth)
      PARAMETER-TABLE
        ptab
      EXCEPTION-TABLE
        etab.
I have read most of the post using Class cl_abap_typedescr=>describe_by_name to get parameter where I have to give correct parameter type.
But my issue is that I also need to know which fields are acting as importing , exporting and changing parameter.
Is there anyway to determine and pass method's paramter type as well ?
Thanks!
Regards,
Ramya

Might be I can use table view VSEOMEPARA

Is there a way to dynamically determine the number of out parameters for a server side procedure?

Hi,
Below is a helper method used for calling a server-side function which loops through the inbound bindVars parameter to populate the function's IN parameters. Is there a way to dynamically determine the IN/OUT parameters based on the procedure name in the stmt parameter? No members of the CallableStatement class seemed promising, but the getParameterMetaData() method in the PreparedStatement class seemed like it could be helpful lead. However, I have not found any detailed descriptions (yet) of how to use it.
protected Object callStoredFunction(int sqlReturnType, String stmt,
Object[] bindVars) {
CallableStatement st = null;
try {
// 1. Create a JDBC CallabledStatement
st = getDBTransaction().createCallableStatement(
"begin ? := "+stmt+";end;",0);
// 2. Register the first bind variable for the return value
st.registerOutParameter(1, sqlReturnType);
if (bindVars != null) {
// 3. Loop over values for the bind variables passed in, if any
for (int z = 0; z < bindVars.length; z++) {
// 4. Set the value of user-supplied bind vars in the stmt
st.setObject(z + 2, bindVars[z]);
// 5. Set the value of user-supplied bind vars in the stmt
st.executeUpdate();
// 6. Return the value of the first bind variable
return st.getObject(1);
catch (SQLException e) {
throw new JboException(e);
finally {
if (st != null) {
try {
// 7. Close the statement
st.close();
catch (SQLException e) {}
James

The PreparedStatement.getParameterMetaData() object is exactly what you need for this task.
Once you have the ParameterMetaData you can ask it how many parameters are present and which mode they are. The parameters are numbered from 1 to n and you can use ParameterMetaData.getParameterMode(1); to get the mode of the 1st parameter. The modes are defined as static values in the ParameterMetaData object. Check out the doc at http://docs.oracle.com/javase/7/docs/api/java/sql/ParameterMetaData.html
Timo

What are the parameters in Call transaction method?

Hi ABAPER'S,
Please give me what are the parameters in call transaction method?
Thanks,
Prakash

Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
Syntax:
CALL TRANSACTION <tcode>
USING <bdc_tab>
MODE <mode>
UPDATE <update>
<tcode> : Transaction code
<bdc_tab> : Internal table of structure BDCDATA.
<mode> : Display mode:
A
Display all
E
Display errors only
N
No display
<update> : Update mode:
S
Synchronous
A
Asynchronous
L
Local update
A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
Prepare a BDCDATA structure for the transaction that you wish to run.
With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
CALL TRANSACTION 'TFCA' USING BDCDATA
MODE 'A'
UPDATE 'S'.
MESSAGES INTO MESSTAB.
IF SY-SUBRC <> 0.
<Error_handling>.
ENDIF.
The MODE Parameter
You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
A Display all. All screens and the data that goes in them appear when you run your program.
N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
The display modes are the same as those that are available for processing batch input sessions.
The UPDATE Parameter
You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
The MESSAGES Parameter
The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
(This example uses a flight connection that does not exist to trigger an error in the transaction.)
DATA: BEGIN OF BDCDATA OCCURS 100.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BEGIN OF MESSTAB OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF MESSTAB.
BDCDATA-PROGRAM = 'SAPMTFCA'.
BDCDATA-DYNPRO = '0100'.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CARRID'.
BDCDATA-FVAL = 'XX'.
APPEND BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CONNID'.
BDCDATA-FVAL = '0400'.
APPEND BDCDATA.
CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
LOOP AT MESSTAB.
WRITE: / MESSTAB-TCODE,
MESSTAB-DYNAME,
MESSTAB-DYNUMB,
MESSTAB-MSGTYP,
MESSTAB-MSGSPRA,
MESSTAB-MSGID,
MESSTAB-MSGNR.
ENDLOOP.
The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
Return codes:
Value
Explanation
0
Successful
<=1000
Error in dialog program
> 1000
Batch input error
System fields:
Name:
Explanation:
SY-MSGID
Message-ID
SY-MSGTY
Message type (E,I,W,S,A,X)
SY-MSGNO
Message number
SY-MSGV1
Message variable 1
SY-MSGV2
Message variable 2
SY-MSGV3
Message variable 3
SY-MSGV4
Message variable 4
Error Analysis and Restart Capability
Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
write out or save the message table
use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

Parameters for opening PDF files in a browser

I read some of the posts about making a text link from an html page to a specific location in a pdf document in the browser. I set up the parameters, as I understand it, according to the document "Parameters for Opening PDF Files." The result from my test took me to the top of page 1, not to the bookmark on page 3 that I specified. See the link below. What is wrong with the parameters?
http://www.tabardtheatre.org/YPASCfolder/2012/SummerYouthProgram2012.pdff#page=3&bookmark= anniejr
You can also go to the website: http://www.tabardtheatre.org/audition.html and click on the text link (in blue).

The PDF Open Parameters do not contain the option to link directly to a bookmark, as was mentioned, but I've developed a script that can add this functionality to your files. Have a look here, if you're interested: http://try67.blogspot.com/2011/06/acrobat-link-to-specific-bookmark-in.html

Registering for Caller Display. Do I need to?

Quick history:
Mod on this forum arranges new deal for me for combined Infinity/Call package.
I agree to new deal on condition that I get everything on my account as it was.
New contract starts (Broadband/Calls/Line Rental) on 10th of September 2013.
My Call Package includes BT Privacy, etc. at no extra cost. See pic below...
A few days later news breaks that BT intend to start charging for the same calling features.
I write to the Mod asking if I will have to start paying the fee for these services. He doesn't reply. Eventually I get a reply (obviously automated) telling me the info is on the website, and links to same.
I write back asking for a proper reply to my question; this time I get a reply from 'Yunus', but it doesn't answer the question, (he only confirms that line rental will go up 6.4%), so I try other means.
I use the price increase checker linked to on the other thread here; it tells me the Infinity/Calls Package will go up, but there is no mention of any changes to my Calling Features prices.
I try Live Chat; holy sh!t, these people are useless! Are they paid to just tell you want to hear?
First guy tells me 'no increase' in any of my prices';
second guy says line rental going up, Infinity going up, but caller features package will not go up as they were included free in the package I signed up for with the Mod here
third, it's a girl; she says everything will go up, and if I choose to leave I need to pay a full year's charges for cancelling.
Plainly, they are not all correct.
All I want to know is, what is going up? When? Do I have to sign up/pre-register for this free year's Caller Display thing? Won't that mean my contracts for BB/Calls, and Line Rental will have different end dates?
I have read the big long thread about the rises, so do not require a repeat of the answers given there as most of them contradict each other anyway, just like Live Chat.
It would be helpful to get a reply from a Mod (preferably the one who signed me up to this new contract in the first place) and not from any of the BT 'groupies'.
Thanks.
Incidentally, I've not had any letter or e-mail informing me of the price rises at all.
I'm a Private person; I respect those who respect my Privacy.

DavidM wrote:
Hi Old_Bear,
Thanks for posting. Not sure what you mean by BT 'groupies' but you can check if you're directly affected by the pricing change by entering your details here.
Cheers
David
Hi David
Old_Bear wrote:
I use the price increase checker linked to on the other thread here; it tells me the Infinity/Calls Package will go up, but there is no mention of any changes to my Calling Features prices.
Been there, done that!
Also spoke to Live Chat - pretty useless!
My questions were:
What else will go up?
Will I start being charged for caller display, etc. when they are clearly included free as part of the package I agreed to sign up for with your colleague?
Do I have to sign up/pre-register to get it for free when BT do start charging?
Will this mean my Line Rental and BB/Calls contracts will have different end dates?
I only want a straight answer to my questions; Customer Service have so far given me 5 different answers.
I'm a Private person; I respect those who respect my Privacy.

How to clear all selection screen parameters before calling transaction?

Hi Experts
 I have a ABAP report that displays data using ALV.
When I double click a cell it calls transaction MB51. Before calling the transaction I need to set some parameters of the selection screen of the transaction.
My code is like below:
<UL>
 <LI>FREE MEMORY ID 'MAT'. "material
 <LI> FREE MEMORY ID 'WRK'. "plant
 <LI> FREE MEMORY ID 'CHA'. "batch
 <LI>* Get the selected ALV row data
 <LI>READ TABLE i_recon INDEX p_selfield-tabindex INTO x_recon.
 <LI>* If link MB51 is clicked then open tcode MB51
 <LI> IF p_selfield-sel_tab_field+8(4) = 'MB51'.
 <LI>* Pass material, plant to the corresponding tcode
 <LI> SET PARAMETER ID 'MAT' FIELD x_recon-matnr.
 <LI> SET PARAMETER ID 'WRK' FIELD p_plant.
 <LI> CALL TRANSACTION 'MB51' AND SKIP FIRST SCREEN.
</UL>
The problem is:
<UL> <LI> 1. First, I run the given transaction before running the report in a separate session with some set of values in the selection screen. For example: plant = AB01, Material = 990001 and Batch = 10001.</LI>
</UL>
<UL>
 <LI> 2. Then in another session I run my report. In the report ALV I have selected a record where plant = AB01, Material = 990001 but Batch is blank. But it opens the transaction with plant = AB01, Material = 990001 and Batch = 10001.
Even though in my ALV record the batch is blank yet it uses the batch value from the memory. That is, the batch value that was given in the transaction earlier. Why it is not getting cleared? I have also used FREE MEMORY ID code in the beginning. But still it is not clearing the values in the memory.
</UL>
<UL>
 <LI>What shall I do to clear all the selection screen parameters before calling the transaction?</LI>
</UL>
<UL>
 <LI>
Thanks
Gopal
</LI>
</UL>
Edited by: gopalkrishna baliga on Aug 11, 2010 10:29 AM

Its because sap memory is globally shared.
Do it like this.
READ TABLE i_recon INDEX p_selfield-tabindex INTO x_recon.
IF p_selfield-sel_tab_field+8(4) = 'MB51'.
perform bdc_dynpro using 'RM07DOCS' '1000'.
perform bdc_field using 'BDC_OKCODE' '=ONLI'.
perform bdc_field using 'MATNR-LOW' x_recon-matnr.
perform bdc_field using 'WERKS-LOW' p_plant.
perform bdc_field using 'CHARG-LOW' p_batch.
perform bdc_field using 'DATABASE' 'X'.
call transaction 'MB51' with i_bdcdata mode 'E'.
endif.
form bdc_dynpro using program dynpro.
clear la_bdcdata.
la_bdcdata-program = program.
la_bdcdata-dynpro = dynpro.
la_bdcdata-dynbegin = 'X'.
append la_bdcdata to i_bdcdata.
endform.
form bdc_field using fnam fval.
 clear la_bdcdata.
 la_bdcdata-fnam = fnam.
 la_bdcdata-fval = fval.
 append la_bdcdata to i_bdcdata.
endform.

Query UCCX database for calls from a specific Caller ID

Hi,
I did some searching and could not find this answer specifically.
I have a request from the call center supervisor to provide a report of all calls coming into the CSQ's showing all of the important data (date, time, answered, not answered, length of call, disposition, etc.) for calls from a specific caller ID for a specific date range.
The caller ID starts with 9XX-XXX-XXXX, so of course UCCX Historical Reports will not display this number as a parameter in the Detailed Call by Call CCDR report because I am limited to the first 32,765 rows. I tried modifying the XML file but have not been successful.
I tried doing a query through the CLI but not sure if I have the query right.
Any insight?
Thank you very much.

I tried modifying the XML file for the Detailed Call CSQ Agent report
ICD_Detailed_Call_CSQ_Agent_en_us.xml with the following:
BEFORE:
SELECT distinct callednumber FROM contactcalldetail
AFTER:
SELECT SKIP 10000 FIRST distinct 20000 callednumber FROM contactcalldetail
Unfortunately, there are no changes in the available parameters shown:
The number starts with a '9', so I need to skip the numbers that start with 408. Any help?

When we have to go for session method, when we have to go for call transact

when we have to go for session method, when we have to go for call transaction method if i have a 3000 records in flat file. which is better? why

Data Transfer
During the process of data transfer, data is transferred into the SAP R/3 System. This transfer is from an external system to SAP R/3 system. Whenever you transfer data from an external system into an R/3 System, you can use data transfer because it is installed and regularly transfers data from an external system into an R/3 System.
As discussed, with the help of BDC, you can transfer the required data from a non-SAP system to an SAP system. For this kind of data transfer you are required to write an ABAP program. This ABAP program would help to export the concerned data to a sequential dataset file. The data in this file has to be stored. This should be stored in a format, which is acceptable to SAP batch input program. But, to transfer data from a SAP system to another SAP system, you can take the aid of RFC or CPI-C.
SAP application supports the data transfer of numerous SAP business objects. The said data transfer program specifies the data format definition, which is necessary to import the data into the R/3 System. There are three methods available for transferring data:
Direct Input:
In this method the SAP function modules execute the consistency checks. However, there are other means of checking with the help of screens. The Direct Input Method has considerable performance advantages.
Call Transaction:
In this method you can check the data consistency with the help of screen logic.
Batch Input Session:
In this method data consistency is checked with the help of screen logic.
Direct Input Method
Among the methods of data transfer through BDC, direct input method is the one that is used, especially in case of transferring large amount of data. In order to enhance the batch input procedure, the system offers you with the direct input technique.
There is a distinction between the batch input technique and this technique. Unlike batch input technique, this technique does not create sessions. Instead, it stores the data directly. Moreover, it does not process screens. The data has to be entered directly into the corresponding database tables. The system calls a number of function modules which execute necessary checks, if any required. In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.
Call Transaction Method
Call Transaction method is another method used for Data Transfer. In this type of method your program will use the ABAP statement CALL TRANSACTION USING in order to run a SAP transaction. In this type external data need not be deposited in a session for being processed later on. Instead, the entire batch input process takes place inline in your program.
Here, the data transfer program must convert the data that has to be transferred into the SAP system. This is as per requirement by the SAP data structure or the transaction which is using it. It is to be remembered that a conversion of the data types may be necessary at different times during the process.
Suppose there is a data type mismatch then you have to convert the data types to type C. In this regard the data transfer program should be capable of exporting the data in SAP format to the sequential file. At the time of uploading the data into the SAP system, the BDC program reads the data from the abovementioned sequential file.
Batch Input Session Method
This is the third method for data transfer. If you use the batch input method to transfer data, then you should remember that an ABAP program has to read the external data which is to be entered in the R/3 System. Subsequently, it stores the concerned data a "batch input session." The batch Input session records the actions which are required in the process of transferring data into the system. This can be done by using normal SAP transactions.
As soon as the program generates the said session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:
System à Services à Batch input. Moreover, you can have the session run in the background processing.
Writing a Data Transfer Program
If you want to write a data transfer program, you have to follow the steps mentioned below.
Firstly, you will analyze the structure of the existing data. Subsequently, your job is to specify the conversions, which are essential to fill the SAP data structures.
Secondly, you have to generate the SAP data structure. In case the program is written in ABAP, you will require only the required tables in the concerned program with the help of TABLES statement.
Thirdly, you will have to initialize the SAP data structure.
Fourthly, fill the structure with data, performing any conversions and error checking that are required.
Finally, you will write the sequential file. In the SAP system this sequential file is typically required for making the data available to the batch input program.
Batch Input Method
Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.
There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.
The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.
The process flows for a batch input are discussed below.
Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.
Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).
Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.
Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.
Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need to be involved.
Error Handling in Batch Input Method
It is found that most problems usually fall into one of the following two categories discussed below.
In this case either required data is missing from the batch-input session or invalid data has been included in the session. Errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database are the possible external causes of this type of problem. Within R/3, the causes for this type of problem include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.
This case mainly includes technical/programming problems. The data is entered by a batch input session by running R/3 transactions non-interactively. Therefore, a typical technical or programming problem is the incorrect identification of one of the data fields in a transaction. Thus, the conversion program may not fill a required data field or may have provided invalid values.
Conclusion
I have gone through the details of batch data communication and various methods used to transfer data. One can make use of BDC to transfer data from a SAP to SAP system. In addition, it can transfer data from a non SAP system to SAP system too. I have discussed the various methods of BDC and the error handling in the respective methods.
Thanks,
Shankar

Parameters for calling PCR Direct Launch

Similar Messages

Maybe you are looking for