博客园_Hahappyppy

期初库存 acc. determination

2011-10-24T02:51:00Z

OBYC-GBB-BSA

http://blog.csdn.net/stone0823/article/details/5116054

本文链接

idoc menu area WEDI

2011-04-06T07:43:00Z

idoc menu area WEDI

本文链接

DO ENDDO. Check 逻辑控制

2011-03-01T06:40:00Z

DO 1 TIMES.

SELECT SINGLE ap_fieldcat FROM /fom/tc_rep_ap INTO lv_structure
WHERE acc_pr = p_acc_pr
AND   report = sy-repid.

CHECK sy-subrc <> 0.

SELECT SINGLE cust_set_id FROM /fom/tc_ap_cust INTO lv_cust_set
WHERE obl_type = /fom/cl_aro_object=>gc_obl_type_for_aro
AND   acc_pr   = p_acc_pr.

CHECK sy-subrc = 0.

SELECT SINGLE impl_class FROM /fom/tc_custset INTO lv_impl_class
WHERE cust_id = lv_cust_set.

    TRY.

CALL METHOD (lv_impl_class)=>get_report_struc
EXPORTING
            iv_repid     = /fom/if_aro_object_acc_pr=>gc_rep_evaluate
          RECEIVING
            ev_structure = lv_structure.
CATCH cx_sy_dyn_call_error.

    ENDTRY.

ENDDO.

本文链接

多条 Message 处理

2010-12-22T08:41:00Z

FUNCTION send_message_direct.
*"--------------------------------------------------------------------
*"*"Local Interface:
*" IMPORTING
*" REFERENCE(IT_RETURN) TYPE BAPIRETTAB OPTIONAL
*" REFERENCE(IV_SEND_IF_ONE) TYPE BOOLEAN DEFAULT ABAP_TRUE
*"--------------------------------------------------------------------

DATA: lt_return TYPE bapirettab.

FIELD-SYMBOLS: <lfs_return> TYPE bapiret2.

lt_return[] = it_return[].

CALL FUNCTION 'MESSAGES_INITIALIZE'
EXPORTING
reset = abap_true.

LOOP AT lt_return ASSIGNING <lfs_return>.
    CALL FUNCTION 'MESSAGE_STORE'
      EXPORTING
        arbgb = <lfs_return>-id
        msgty = <lfs_return>-type
        msgv1 = <lfs_return>-message_v1
        msgv2 = <lfs_return>-message_v2
        msgv3 = <lfs_return>-message_v3
        msgv4 = <lfs_return>-message_v4
        txtnr = <lfs_return>-number
      EXCEPTIONS
        OTHERS = 0.
ENDLOOP.

CALL FUNCTION 'MESSAGES_SHOW'
    EXPORTING
      send_if_one = iv_send_if_one
      i_use_grid = abap_true
      show_linno = abap_false
    EXCEPTIONS
      OTHERS      = 0.

ENDFUNCTION.

本文链接

How to upload a file via ABAP RFC with Webdynpro ?

2010-12-16T07:35:00Z

Xiaopeng Tan

Posts: 32
Registered: 7/18/05
Forum Points: 6

How to upload a file via ABAP RFC with Webdynpro ?
Posted: Nov 23, 2005 10:45 PM

Hi everyone,
I have the follwing problem.
I`m currently creating a webdynpro DC to upload files to a mySAP CRM system via RFC.
The RF-module is already available at the backend side and I have imported it as a model. The ABAP module interface looks like this:

*"  IMPORTING
*"     VALUE(IV_CASE_GUID) TYPE  SCMG_CASE_GUID
*"     VALUE(IV_FILENAME) TYPE  SDOK_PROPV DEFAULT 'Case Document'
*"     VALUE(IV_MODELNODE) TYPE  STRINGVAL DEFAULT '19'
*"     VALUE(IV_FILE_CONTENT_BINARY) TYPE  SDOKCNTBINS OPTIONAL
*"  EXPORTING
*"     VALUE(EV_MESSAGE) TYPE  BAPI_MSG
*"  EXCEPTIONS
*"      UPLOAD_FAILED

The parameter IV_FILE_CONTENT_BINARY of TYPE SDOKCNTBINS is imported into the webdynpro model as input structure ( 0..n cardinality and of collectiontype list) with one child attribute (line) which can be fed with a byte array (data type RAW with length 1022 on ABAP side).
I`m not really familiar with ABAP. To my understanding the structure IV_FILE_CONTENT_BINARY takes lines of byte arrays and that list of arrays will be uploaded with the RFC, right?
Now in my Webdynpro view I implemented the standard FileUpload UI element from which I got a IWDResource object.
Reading the IWD Resource object I got a inputStream from the file I`d like to upload.
Now my question is: how to get the IV_FILE_CONTENT_BINARY list filled with the inputStream?
I at least figured out that reading a byte array and put it into the structure would pretty much look like the follwing:


//create new list object
Sdokcntbin bin = new Sdokcntbin();   //create a temporary byte array with length of the line to be inserted into the list.
byte[] b = new byte[bin.getLine().length];   **read the inputStream into the byte array**
inputStream.read(b); ???   //write the byte array into the list
bin.setLine(b);   //add list to input node for RFC
ModelNode.addIv_File_Content_Binary(bin);

Do I need to create a loop to read the file binary as byte array segments of length 1022 each or am I wrong here totally?

Valery Silaev

Posts: 2,972
Registered: 3/3/04
Forum Points: 7,127

Re: How to upload a file via ABAP RFC with Webdynpro ?
Posted: Nov 24, 2005 10:15 AM in response to: Xiaopeng Tan

Xiaopeng,
Yes, you have to read input stream by 1022 bytes chunk, and create Sdokcntbin per chunk.
Something like this:

final int chunkSize = 1022;
final byte[] chunk = new byte[chunkSize];
final BufferedInputStream in 
  = new BufferedInputStream(resource.getInputStream());
try
{
  int size = -1;
  while ( (size = in.read(chunk, 0, chunkSize)) > 0 ) 
  {
    // If last chunk is partial, pad rest with zeros
    if ( size < chunkSize )
      Arrays.fill( chunk, size, chunkSize, 0);   //create new list object
    final Sdokcntbin bin = new Sdokcntbin();
    //write the byte array into the list
    bin.setLine(chunk);
    //add list to input node for RFC
    <ModelObject>_Input.addIv_File_Content_Binary(bin);
  }
}
finally
{
  in.close();
}

Valery Silaev
EPAM Systems
http://www.NetWeaverTeam.com

Message was edited by: Valery Silaev

Xiaopeng Tan

Posts: 32
Registered: 7/18/05
Forum Points: 6

Re: How to upload a file via ABAP RFC with Webdynpro ?
Posted: Nov 24, 2005 11:51 AM in response to: Valery Silaev

Hi Valery,
That's exactly what I was looking for. It's working now. Perfect!
Thank you very much!
Best regards,
Xiaopeng

http://forums.sdn.sap.com/thread.jspa?threadID=84501

本文链接

Temporary Post Used For Theme Detection (3f076c7b-c23c-44e1-8634-4158040f52b8 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

2010-12-16T06:20:00Z

This is a temporary post that was not deleted. Please delete this manually. (f10b650b-bd71-4f1c-86ab-156611a1163b - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

本文链接

If 1=2. What is this code about? MESSAGE where used list

2010-12-01T07:29:00Z

http://www.saptechnical.com/Tips/ABAP/if1=2.htm

We all might have seen the code "IF 1=2. ....do this...EndIF" and we also know that this code never turns true. The main purpose of such code is for "Maintainability" of the program. Confused?? Read the following:

Depending upon the scenario, we would either issue the messages in the program using MESSAGE statement or sometimes might have to call the standard function module MESSAGE_PREPARE to prepare the whole message and use it wherever required.

CALL FUNCTION 'MESSAGE_PREPARE'
   EXPORTING
     msg_id = msg_id
     msg_no = msg_no
     MSG_VAR1 = sy-msgv1
     MSG_VAR2 = sy-msgv2
     MSG_VAR3 = sy-msgv3
     MSG_VAR4 = sy-msgv4
IMPORTING
     MSG_TEXT = tdoc-text
EXCEPTIONS
     FUNCTION_NOT_COMPLETED = 1
     MESSAGE_NOT_FOUND = 2
     OTHERS = 3.

Assume that we have defined custom message class for issuing the messages. If we have to modify certain message in this message class, we first need to check for the where-used list of the message to study the impact of the message change. If the message is issued using the MESSAGE statement in any program, then that program would appear in the where-used list. But if the message is used in the program using the FM MESSAGE_PREPARE or any similar function module, then this program would not appear in the where-used list. So in order to have this program include in the where-used list, we would code the following after the call to the function module MESSAGE_PREPARE.

IF 1=2.

Message E003(xx).

ENDIF.

Since the check "IF 1=2" never gets true, the message would never trigger in the program and this program would appear in the where-used list of that message.

本文链接

Trace tcode: SAT ST12 SE30 ST05

2010-11-29T01:53:00Z

Imagine you change an order in VA02 and after clicking a specific button (e.g. the ATP (available to promise) check) it takes a while. Now you wonder what happens when you click this button and how you could trace exactly this click. In this blog we will explain how to trace a single dialog step with the "Particular Units" option in ST12.

Before you start:

Please read the "Before you start" section in this blog first:

https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15702

We'll use the "Current Mode" scenario and the same tracing options as described in the above mentioned blog.

ST12 - Tracing a single step

After filling in the transaction and a comment for the trace (nr. 1 in figure 1) we select the "Particular units" option. Note: this option is only available in the "Current Mode" Scenario. All other options are set like described in the above mentioned blog.

Figure 1 - Trace with particular units

Executing the trace for particular units

We are ready to start our trace (nr. 3 in figure 1).

All we have to do is to mark the part we want to trace while we step through VA02. The prerequisite is that you switch on the "Particular Units" option in ST12 as shown above.

If you look at figure 2 which shows the steps we execute in VA02 to do an ATP check you can see that there are some steps that we don't want to trace:

We don't want to trace the whole execution (dashed black arrow) between T1 and T2 but only the ATP check (solid red arrow) between T1a and T1b. Note: As you can see in figure 2 the ST05 trace (dashed green arrow) records the whole execution of the transaction but not only particular units of it.

Figure 2: Executing VA02 with current mode particular units

While executing VA02 we have to mark which parts of the execution should be traced with the ABAP trace:

Figure 3: VA02

After you start the trace (nr. 3 in figure 1) VA02 (or the transaction /program you entered in the corresponding transaction / program field in ST12 in the main screen) will show up. Since we switched on the "Particular Units" nothing is traced so far. Now we enter the order and select it. During selection and when we do our changes, nothing will be recorded in the ABAP trace yet. Right before we click on the ATP check button (nr. 2 in figure 3) we type "/ron" in the ok-code field (this is the field where you type in the transactions e.g. ST12 as well) and press ENTER (nr. 1 in figure 3). This marks that the ABAP trace should be recorded from now on. This is confirmed with the message "Runtime analysis enabled" at the bottom of the screen (nr. 1 in figure 3).

After that we execute the ATP check by clicking on the button (nr. 2 in figure 3). The next screen shows the result of the ATP check. We have to set the second marker now that indicates we want to stop trace recording so that nothing else is traced from this point on. We enter "/roff" in the transaction code field (nr. 3 in figure 3). We get the message "Runtime analysis disabled" at the bottom of the screen (nr. 3 in figure 3). After this, nothing else (e.g. clicking on save) will be recorded in the ABAP trace any more. If you return to ST12 and open the ABAP trace, it will only contain these parts of the execution that were running between the markers "/ron" and "/roff". Note that the performance trace (ST05) captures the whole execution of the transaction as shown with the dashed green line in figure 2.

Alternatives for the "/ron" and "/roff"

In dialog transactions you can either work with the ok codes "/ron" and "/roff" like we have seen above. Alternatively you can use the menu path:

System - Utilities(H) - Runtime Analysis - Switch on

System - Utilities(H) - Runtime Analysis - Switch off

In your own developments (e.g. for programs running in background) you can even do it in the ABAP code with these 2 commands:

SET RUN TIME ANALYZER ON.

SET RUN TIME ANALYZER OFF.

This blog demonstrated the "Particular Units" option which is very useful if you want to trace a specific part of a program e.g. a single transaction step in dialog transactions.

And with special thanks to Sandra Rossi:

See how the above mentioned ok codes can be used in modal popup windows:

http://wiki.sdn.sap.com/wiki/display/ABAP/SAPGUI+shortcuts

More information on ST12 can be found here:

ST12 WIKI and Blogs:

http://wiki.sdn.sap.com/wiki/display/ABAP/Single+Transaction+Analysis

Books:

http://www.sap-press.com/product.cfm?account=&product=H3060

http://www.sap-press.de/1821

本文链接

Save FM parameters as SE37 test data within a debugging session

2010-11-29T01:52:00Z

- Set a breakpoint in the function module
- when the debugger stops in the function module copy all importing, changing parameters and tables from the function module into your variables section
- in the variables section click on the tools icon
- choose option 'Save parameters as Test data (SE37)
- you get a popup where you can enter the name for your test variant
- confirm
-when you now run SE37 you will find your variant, which will populate the interface with all the data

本文链接

利润中心资产负债表 / profit center B/S statement

2010-11-22T02:51:00Z

2010-11-22T02:51:00Z2010-11-22T02:51:00ZHahappyppyhttp://www.cnblogs.com/mysap/

本文链接

博客园_Hahappyppy

期初库存 acc. determination

idoc menu area WEDI

DO ENDDO. Check 逻辑控制

多条 Message 处理

How to upload a file via ABAP RFC with Webdynpro ?

Temporary Post Used For Theme Detection (3f076c7b-c23c-44e1-8634-4158040f52b8 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

If 1=2. What is this code about? MESSAGE where used list

Trace tcode: SAT ST12 SE30 ST05

Save FM parameters as SE37 test data within a debugging session

利润中心 资产负债表 / profit center B/S statement

利润中心资产负债表 / profit center B/S statement