How to create Leader Lines for Pie Chart Labels

I like Numbers but the restrictions they force are sometime just too much.
Example: Labels
The restriction of only being able to move a label of a wedge on a parallel axis is ridiculous. Here Excel clearly out shines Numbers.
I want an option to add a leader to a "Value" label so I can move it away from an area that is too crowded or the space for it is limited.
Yes, I know I could just not turn Labels on in Numbers and then use a text box to place the value anywhere I wish and then draw in a leader to fit my needs. But that is no solution just a horrible work-around.
Come on Apple. You've started a nice product here but gee-whiz, golly-gee, it's hard to adopt your products as MS replacements when so many basic features are missing.

AlbertEinstein,
And I don't understand why you are even posting here. What in your reply was useful to my issue? Seriously, if you're here on this board just to spout opinions, might I suggest you take up blogging.
As for me, I'm here to try to find an answer to my problem. If you're knowledgable and know that it can't be done then just saying so the way Badunit did. It wasn't the answer I was looking for but at least he was trying to be constructive.
OK, so to your point. You've been using spreadsheets since Visicalc, good for you. My issue isn't with the spreadsheet part of Numbes, but rather with the charting technology.
Well I was a draftsperson when all there was, was boards and T-Squares. And a common rule is if your information is too close, overlaps, etc to be understood then you use a leader to move it to an area where it is not so cluttered.
Your issues with OpenOffice and MS Office I can't address because I'm not interested in either of those products within this thread.
So please if you have a suggestion as to how to solve my issue then I welcome your comments. But if you're here just to "complain" about others complaining I can just ask, what's your point?

Similar Messages

How to create a tomato shape pie chart?

Hi,
I google around to find a way to create a custom-shape pei chart (a tomato with 3 percentage numbers in it, say 25% 25% and 50%). But I always got stuck when trying to creat the mask, which i have no clue....
Could some computer expert here help me to understand it?
thanks
sz

arabidopsis10 wrote:
Hi,
I google around to find a way to create a custom-shape pei chart (a tomato with 3 percentage numbers in it, say 25% 25% and 50%). But I always got stuck when trying to creat the mask, which i have no clue....
Could some computer expert here help me to understand it?
thanks
Hi sz,
Although the Numbers User Guide (which you should find in the iWork 08 folder in your Applications folder) does say, "You can also drag an image to mask a shape with an image," I didn't have any success when trying to do so.
The best I was able to do was to place the pie chart in front of or behind a tomato image, then set the transparency of whichever was in front to allow the other to show through. Although I'm not really happy with the result, here's a sample, with the chart in front. The chart's Fill has been set to None, and the opacity of the 'slice' colours has been set to 30%. The colours used for the slices are shown in the chart's legend.
You might achieve an improved result by experimenting with the colours and opacity settings.
Regards,
Barry

How to create matreial document for ten line items (10 documents) by BAPI

Hi
how to create matreial document for ten line items (10 documents) by BAPI_goodsmvt_create
i created but it gives error as "no ites were transferre
and i need code also.
thanks in advance

Prabhu Peram wrote:>
> >
Gareth @ Atos Origin UK wrote:
> > Prabhu,
> >
> > You have been on SDN a long time and have a decent amount of points - why do you feel the need to simply cut and paste standard SAP documentation? _-----> I least bother abt the Points, and i never ask somebody to give points to me , if u have any doubt on it , u can check all my postings ? All it does is fill up the SDN servers with replicated data which the original poster could quite easily access themselves via SE37----> Sorry I have seen ur Posting/Reply,dont assume that i do copy & paste for sake of Points.Njoy SAP.>
> > Gareth.
>
>
>
> regards
> Prabhu
Prabhu.
I didn't question you about points at all - I was making the point that you have been on SDN a long time and have a lot of points. Therefore you should know better than to simply cut and paste standard SAP help. If you don't copy and paste for sake of points, what do you do it for? It serves no purpose other than to fill up the servers here on SDN. The original poster appears to have access to a SAP system and SE37 and wants to know how to call a BAPI - they can easily go to SE37 and read the documentation themselves. Posting it here just adds noise and makes searching harder, as well as taking up more and more space on SDN servers.
Gareth.

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

How to create lead follow up opportunity....

Hello,
How to create lead follow up opportunity automatically... Also my clients need is when we change the status of Lead from Open or In-Process or Won to Completed then an automatic email should go to the employee responsible in the lead.
Please help me in this.... I tried doing this by creating Action profile & assigning that action profile to transaction type but didn't get the expected result.
I would really appreciate some one help on this.... Please describe it in steps for automatic Opportunity creation & also for email.
Thanks,
Ajeet

Using action is correct approach. You just have to configure action properly. For follow-up use in action 'method call' and use method 'copy_document' and as parameter specify transaction type that you want to be created as follow-up.
For mail, you can use in action trigger_alert method.

How to create transaction code for maintenance view

hai friends,
i hope every thing goes good.
i have doubt, how to create transaction code for maintenance view. I created view for tranperant table and now i want to create transaction code for the view.
i tried and i donot know the screen number and program name and where can i give the view name.
if any one know please post in details.
thanks in advance.

Hi Elam,
You need to create a "Parameter Transaction".
What this means is that you will have a transaction (let's call it "ZMAINT") which calls "SM30" and passes in your table name.
Go to transaction SE93 and enter your new transaction code. Enter in the Tcode description and choose "Transaction with Parameters" (it shouldbe the last radio button).
Enter in the default transaction "SM30" and tick the "Skip Initial Screen" check box. Hit Enter.
Now scroll to the bottom of the screen and you will see a Table Control where you will need to enter in the values to the SM30 selection screen.
Because you hit ENTER, the program will have loaded in the Selection Screen parameters into it's memory. Hit the drop down for "Name of Screen Field" and select "VIEWNAME" and then enter in your Z Table in the "Value" column.
Now go to the next line and hit the drop down and select "UPDATE" in the "Name of Screen Field". Enter in a "X" in the value column.
Now save the transaction and there you have it.
Hope this helps.
Cheers,
Pat.
PS. Kindly assign Reward Points to the posts you find helpful.

How to create internal table for a structure in BSP

hi ,
I have created a Structure in BSP.I want to create an internal table for that Structure. But in my coding ie.
<% data: begin of itab_1 .
                 include type zuvendstr.
                 data:end of itab_1.
                 data wa_str like line of itab_1.
                 loop at itab_1 into wa_str. %>
                <tr>
                 <td><%=wa_str-name%> </td>
                       <%endloop.%>
In this zuvendstr is Structure ,wa_str is workarea and itab_1 is an Internal table.But it is showinng an error that itab_1 is unknown.But we cannot define internal tables for an Structure in Page Attributes.So,please resolve how to create internal table for Structure in BSPS

Hi,
You can define itab_1 like this (assuming zuvendstr is a structure type):
DATA: itab_1 TYPE TABLE OF zuvendstr.
Regards,
Tanguy

How to create Search Help for a field in Table control !!

Hello Friends,
              I like to know - How to create Search Help for a field in Table control. Is it possible, if it is please share ur knowledge, I wud be happy if U provide some source code example for this.
Thanks,
Senthil

Check the sample code:
*& Include           ZSRO_MPRN_SEARCH                                 *
MODULE PSTLZ_F4 INPUT
MODULE pstlz_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
        stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR:   lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl     = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = c_x
      determine_loop_index = c_x
    TABLES
      dynpfields           = lt_dynpfields
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
    MOVE lt_dynpfields-fieldvalue TO ws_outcode.
    ws_len = STRLEN( lt_dynpfields-fieldvalue ).
    IF ws_len GE 7.
      ws_len = ws_len - 3.
     ws_icode = ws_code+ws_len(3).
      lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
      CONCATENATE lt_dynpfields-fieldvalue '%'
          INTO ws_outcode.
      CONDENSE lt_dynpfields-fieldvalue.
   REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
    ELSE.
      CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
        INTO ws_outcode.
    ENDIF.
   ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR:   lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl     = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
    TABLES
      dynpfields           = lt_dnpfields
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode.
    ELSE.
MPRN blank and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1.
    ENDIF.
ELSE.
MPRN exist and Post code exist
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode AND
                   mprn EQ lt_dnpfields-fieldvalue.
    ELSE.
MPRN exist and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE mprn EQ lt_dnpfields-fieldvalue.
    ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'MPRN'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select MPRN'
      value_org       = 'S'
    TABLES
      value_tab       = i_mprn1 "lt_mprn
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
    IF sy-subrc EQ 0.
Updating post code
      CONCATENATE i_mprn1-outcode i_mprn1-incode
                    INTO ws_postcode
                         SEPARATED BY space.
      MOVE ws_postcode TO i_mprn-post_code.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
      ws_dynpfld-fieldvalue = ws_postcode .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
Updating MPRN
      MOVE i_mprn1-mprn TO i_mprn-mprn.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-MPRN'.
      ws_dynpfld-fieldvalue = i_mprn1-mprn .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
    ENDIF.
ELSEIF sy-subrc EQ 2.
    MESSAGE s005(zspa) WITH ws_postcode .
ENDIF.
ENDMODULE.                    "PSTLZ_F4 INPUT
MODULE MPRN_F4 INPUT
MODULE mprn_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
       stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR:   lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl     = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = c_x
      determine_loop_index = c_x
    TABLES
      dynpfields           = lt_dynpfields
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
    MOVE lt_dynpfields-fieldvalue TO ws_outcode.
    ws_len = STRLEN( lt_dynpfields-fieldvalue ).
    IF ws_len GE 7.
      ws_len = ws_len - 3.
     ws_icode = ws_code+ws_len(3).
      lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
      CONCATENATE lt_dynpfields-fieldvalue '%'
          INTO ws_outcode.
      CONDENSE lt_dynpfields-fieldvalue.
   REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
    ELSE.
      CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
        INTO ws_outcode.
    ENDIF.
   ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR:   lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl     = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
    TABLES
      dynpfields           = lt_dnpfields
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode.
    ELSE.
MPRN blank and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1.
    ENDIF.
ELSE.
MPRN exist and Post code exist
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode AND
                   mprn EQ lt_dnpfields-fieldvalue.
    ELSE.
MPRN exist and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE mprn EQ lt_dnpfields-fieldvalue.
    ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'MPRN'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select MPRN'
      value_org       = 'S'
    TABLES
      value_tab       = i_mprn1 "lt_mprn
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
    IF sy-subrc EQ 0.
Updating MPRN
      MOVE i_mprn1-mprn TO i_mprn-mprn.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-MPRN'.
      ws_dynpfld-fieldvalue = i_mprn1-mprn .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
     ws_dynpfld-stepl = mprn-current_line.
**code changed by laxman 10.08.2005
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
Updating post code
      CONCATENATE i_mprn1-outcode i_mprn1-incode
                    INTO ws_postcode
                         SEPARATED BY space.
      MOVE ws_postcode TO i_mprn-post_code.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
      ws_dynpfld-fieldvalue = ws_postcode .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
     break gblap0.
     ws_dynpfld-stepl = mprn-current_line.
     LOOP AT i_mprn.
       MOVE i_mprn1-mprn TO i_mprn-mprn.
       MOVE ws_postcode TO i_mprn-post_code.
       MODIFY i_mprn INDEX
                mprn-current_line." transporting MPRN POST_CODE.
     ENDLOOP.
**code changed by laxman 10.08.2005
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
    ENDIF.
ELSEIF sy-subrc EQ 2.
    MESSAGE s006(zspa) WITH i_mprn1-mprn .
ENDIF.
ENDMODULE.                    "MPRN_F4 INPUT
MODULE GNTC_F4 INPUT
MODULE gntc_f4 INPUT.
DATA: BEGIN OF lt_gntc OCCURS 0,
          gntc LIKE iflot-zzgntc,
        END OF lt_gntc.
CLEAR:   lt_returntab, lt_gntc.
REFRESH: lt_returntab, lt_gntc.
lt_gntc-gntc = 'DM'.
APPEND lt_gntc. CLEAR lt_gntc.
lt_gntc-gntc = 'NDM'.
APPEND lt_gntc. CLEAR lt_gntc.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'ZZGNTC'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select Gas Nomination Type Code'
      value_org       = 'S'
    TABLES
      value_tab       = lt_gntc
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    i_mprn-dm_ndm = lt_returntab-fieldval.
ENDIF.
ENDMODULE.                    "GNTC_F4 INPUT
*&      Module mprn1_f4 INPUT
      text
MODULE mprn1_f4 INPUT.
DATA: lt_f4          TYPE ddshretval OCCURS 0 WITH HEADER LINE,
        lt_returntab1 LIKE ddshretval OCCURS 0 WITH HEADER LINE,
        lt_dynpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE,
        lt_dnpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE.
DATA: stepl1 TYPE systepl,
        stepl_index1 TYPE systepl.
DATA : i_dnpfld1      LIKE dynpread OCCURS 0 WITH HEADER LINE,
         ws_dyname1     LIKE d020s-prog,
         ws_dynumb1     LIKE d020s-dnum,
         ws_dynpfld1    LIKE dynpread.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
         lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
         stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields1-stepl     = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
      determine_loop_index = 'X'
    TABLES
      dynpfields           = lt_dynpfields1
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
    EXPORTING
      tabname           = 'IFLOT'
      fieldname         = 'I_MPRN-MPRN'
      searchhelp        = 'ZS_MPRN_PC'
      dynpprog          = sy-repid
      dynpnr            = sy-dynnr
    TABLES
      return_tab        = lt_f4
    EXCEPTIONS
      field_not_found   = 1
      no_help_for_field = 2
      inconsistent_help = 3
      no_values_found   = 4
      OTHERS            = 5.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-mprn.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
    ws_dynpfld1-fieldvalue = i_mprn-mprn.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-post_code.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
    ws_dynpfld1-fieldvalue = i_mprn-post_code.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDMODULE.                 " mprn1_f4 INPUT
*&      Module pstlz1_f4 INPUT
      text
MODULE pstlz1_f4 INPUT.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
          lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
          stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-MPRN'.
lt_dynpfields1-stepl     = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
      determine_loop_index = 'X'
    TABLES
      dynpfields           = lt_dynpfields1
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
    EXPORTING
      tabname           = 'IFLOT'
      fieldname         = 'I_MPRN-POST_CODE'
      searchhelp        = 'ZS_MPRN_PC'
      dynpprog          = sy-repid
      dynpnr            = sy-dynnr
    TABLES
      return_tab        = lt_f4
    EXCEPTIONS
      field_not_found   = 1
      no_help_for_field = 2
      inconsistent_help = 3
      no_values_found   = 4
      OTHERS            = 5.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-post_code.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
    ws_dynpfld1-fieldvalue = i_mprn-post_code.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-mprn.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
    ws_dynpfld1-fieldvalue = i_mprn-mprn.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDMODULE.                 " pstlz1_f4 INPUT
Regards,
Prakash.

How to create a border for a paragraph ?

Can anyone tell me how to create a border for a paragraph ? Is this even possible without creating a table ?
I would like to have the page header with a single line below it and the page footer with a single line above it. Inserting a line seems to force unnecessary space above of below the line and using a table seems to force a blank line below the table also creating unnecessary space.
Thanks

Thanks, I had the problem with this approach that the line never appeared on each page but adding to the section master would fix it.
Still being able to set a border would be good! I did try using the text box but the border options are pretty inflexible. I was unable to just set the top or bottom borders. Did I miss something basic here or is this option just not available ?
Any idea if this is coming in a future release ?

How to create a Tip for a field in a Descriptive Flex Field in Self Service

How to create a Tip for a field in a Descriptive Flex Field in Self Service ?
Example :
For Address
Each Address Line should have one Tip.
What should I do ?
Thanks,
John

Hi John,
It seems you have created Address Location DFF in self service in OA Framework.....
I have created a Address Location flex in OA Framework . It dipslays the segments properly but i dont want to display the segments if they dont have any value.
I only want to display segments with values . The segments with null values should not display at all...
i.e , if Address Line 2 value is null , it should not display Address Line 2..
If you have done this, pls let me know how to go abt it.
Thanks in Advance,
Tanveer

How to create user dsn for microsoft access driver(*.mdb,.*accdb) in 64 bit

hi,
how to create user dsn for microsodt access driver(*.mdb,*.accdb) using command line in 64 bit.
i have installed 64 bit drivers and when use following command
C:\Windows\System32>odbccad.exe CONFIGDSN "Microsoft Access Driver (*.mdb,*.accdb)" "DSN=GLDatabase|Description=GL Data Source|DBQ=C:\DataBase\1.mdb"
CONFIGDSN:'unable to create a datasource for the "Microsoft Access Driver (*.mdb,*.accdb)" component not found in the registry with the error code -2147467259
but it works with C:\Windows\SysWow64

yes i have installed Microsoft Access Database engine 2010 redistributale => AccessDatabaseEngine_x64.exe
i can able to create user dsn using odbccad32.exe in system32 folder but using command line its not working
C:\Windows\System32>
odbccad.exe CONFIGDSN "Microsoft Access Driver (*.mdb,*.accdb)" "DSN=GLDatabase|Description=GL Data Source|DBQ=C:\DataBase\1.mdb"
CONFIGDSN:'unable to create a datasource for the "Microsoft Access Driver (*.mdb,*.accdb)" component not found in the registry with the error code -2147467259

Cannot create opportunity lines for an opportunity using Web Services 2.0

When working with Web Services 2.0 API every object is exposed without any child objects, this means that if we want to query/update/create/delete child objects that child object has to be exposed via WSDL.
I searched for the opportunity lines child object (also known as revenue lines) in the available WSDL's in the application and also in the documentation and I can’t find it anywhere.
I also checked the opportunity WSDL and it does not contain any reference to the opportunity lines?
How do I create opportunity lines for an opportunity using the Web Services 2.0 API???

When working with Web Services 2.0 API every object is exposed without any child objects, this means that if we want to query/update/create/delete child objects that child object has to be exposed via WSDL.
I searched for the opportunity lines child object (also known as revenue lines) in the available WSDL's in the application and also in the documentation and I can’t find it anywhere.
I also checked the opportunity WSDL and it does not contain any reference to the opportunity lines?
How do I create opportunity lines for an opportunity using the Web Services 2.0 API???

How to create an RFC for MIGO transaction?

How to create an RFC for MIGO transaction?
I want my RFC to accept all details as accepted in MIGO transaction.
For the entered PO no, display the materials against it and allow user to enter the quantity for the same.
Then the user should be able to post the PO by executing the RFC.
Kindly revert asap.
Thanx in advance,
Bhakti

Put good movement header data in structure header
l_header-pstng_date = sy-datum.
l_header-doc_date = sy-datum.
l_header-ver_gr_gi_slip = space.
Assign goods movement code
l_wa_goodsmvt_code-gm_code = c_gm_code.
Add material, plant, and other line item details in
goods movement item table
l_wa_goodsmvt_item-material = l_wa_selected-matnr.
l_wa_goodsmvt_item-plant = l_wa_selected-werks.
l_wa_goodsmvt_item-stge_loc = l_wa_selected-lgort.
l_wa_goodsmvt_item-batch = l_wa_selected-charg.
l_wa_goodsmvt_item-move_type = l_wa_selected-mov_type.
l_wa_goodsmvt_item-entry_qnt = l_wa_selected-deviceid.
l_wa_goodsmvt_item-entry_uom = l_wa_selected-meins.
l_wa_goodsmvt_item-move_plant = l_wa_selected-zwerks.
l_wa_goodsmvt_item-move_stloc = l_wa_selected-zsloc.
l_wa_goodsmvt_item-move_batch = l_wa_selected-rec_batch.
l_wa_goodsmvt_item-serialno_auto_numberassignment = space.
APPEND l_wa_goodsmvt_item TO l_i_goodsmvt_item.
CLEAR l_wa_goodsmvt_item.
l_wa_serial_num-matdoc_itm = l_c_mat_doc_item.
l_wa_serial_num-serialno = l_wa_selected-sernr.
APPEND l_wa_serial_num TO l_i_serial_num.
CLEAR l_wa_serial_num.
To call BAPI BAPI_GOODSMVT_CREATE to transfer material of transfer
type one step
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
    EXPORTING
      goodsmvt_header       = l_header
      goodsmvt_code         = l_wa_goodsmvt_code
    IMPORTING
      goodsmvt_headret      = l_goodsmvt_headret
    TABLES
      goodsmvt_item         = l_i_goodsmvt_item
      goodsmvt_serialnumber = l_i_serial_num
      return                = l_i_return.
cheers
Aveek

How to create an app for wireless distribution?

Hello!
I have a Professional Account of DPS.
How to create an app for wireless distribution?

I would also like to know this as well. More like which product in your family should I use to create an app for wireless distribution? If no answers, then this would lead me to believe I made the wrong purchase...

How to create a macro for a planning type in MC8b transaction

Hi,
I am presently working for a product allocation demand, which have a information structiure with characteristic and key field.
the characteristic are production allocation quantity, incoming order quantity, and open order quantity.
i have created a planning type in which the data updation takes from the excel file to the planning type in mc95.
but i need to create a macro for this planning type .
can any body give the details information how to create a Macro for a planning type.
Thanks and regards
GopalKrishna

Dear Gopal
May be the link would be helpful to you.
[Planning Types and Macros|http://help.sap.com/saphelp_46c/helpdata/en/a5/631cc443a211d189410000e829fbbd/frameset.htm]
Drill down the left tab once you opened the link, for more information.
Thanks
G. Lakshmipathi

How to create Leader Lines for Pie Chart Labels

Similar Messages

Maybe you are looking for