FM: GUI_DOWNLOAD not picking initial zero

Hi Experts,
I am using FM : GUI_DOWNLOAD for downloading material Master to PC...but material number is downloaded without initial zero's...like
if Meterial number is : 005646 and 00012AP00...Then it is downloaded as :
5645 and  00012AP0 ( this number is downloaded as it is because it is alpha numeric )
Please advice :
I have searched SDN many of them have commented to concatenate material number with special characteristics...but I can't go with this because..after downloading user will upload the same ..so it will be big probs.
Please advice.
Karthik.R

Hi Karthik,
You have to check Material value in 2 ways.
First you check the value in debug mode, the material value comes with leading zeroes or not.
1. if it comes with zeroes then you do settings in excel format. (Format cells -> Text)
2. if its not come with zeroes then you use FM Conversion_Exit -
to download with zeroes.
please check......surely u will get output.

Similar Messages

  • PO not picking up the Price from Info Record ???

    Hi,
    Pricing Procedure and the Schema Grp is defined in Schema Determination in SPRO.
    Schema Grp has been assigned in the Vendor Master.
    Price has been maintained in the PB00 condition type in the Condition Supplements screen, but shows 'Zero' in the 'Purchasing Org. Data 1' screen of Info Record.
    However, while creating PO the system does not pick up the Price from the Info Record and both the Condition Types PB00 and PBXX appears and display the Amount as 0.00 ? Also the system does not take the value entered in the 'Net Price' field and the Price can only be entered manually in the Conditon Type in the Conditions Tab ?
    Can anyone help in resolving this issue ?
    Lucky.

    Hi Lucky
    1.Routine 6
    This is an example of a pricing requirement.  This requirement is met if the condition exclusion indicator is not equal to 'X'.  <b>This requirement can be assigned to a condition type in the pricing procedure to ensure that it is not accessed when a condition record with exclusion indicator 'X' has already been found</b>.  Condition exclusion is a general tool that can be used to exclude conditions from pricing based on previous conditions that have been found in the pricing procedure.  This requirement is intended for use in MM pricing versus SD pricing.  For SD pricing, a variation of requirement '2' should be used which would also check to see if the item category is relevant for pricing
    2. You have define all your supplementory condition in supplementory pricing procedure and you have to assign this supplementory procedure to your Condition type PB00.Then all these conditions will be displayed at item level for selection in drop down.
    Since the supplementory conditions are dependent on PB00, you have assign to the PB00.
    If you maintain the values for these conditions in info record, these values will be copied from info to PO.
    Regards
    Ramakrishna

  • Gross Price is not picked up upon creation of a requisition from a network!

    Hi gurus,
    I would like to seek for help, actually problem is related in SD but I pose this thread here because it is related in debugging issue.
    do you know about "perform ROW_OUT " function? we have a bug that is very rare, when user select gross type with figures (ei. 1000, or any number).. system will not pick up the value instead it will be default in ZERO, but when user try to select again it output the correct expected result,,I debug it a dozen times but i cant catch the zero issue, *(-creating watch point wherein TBTWR = 0 and TBTWR <> 0 and the last point of intersection is in row_out sunction and MOVE-CORRESPONDING IX_ESLL to: ESLL) /* Is there someone OF you encountered this ?? if theres one please give some insight on how you pin point the problem in system .. note: all related program and process here is all standard (No custom program involve)..
    Cheers,
    Mark

    Hi
    Generally for posting FI documents (which is what this T Code does) , M alone is used which is the standard SAP system functionality. For other purposes like valuation, translation, etc. we can have different exchange rate types.
    Jayaram

  • Access Not Made (Initialized Field)

    Hello Experts,
    I have come across a generic problem. I have defined a new field (material Type - MTART) in the field catalog and included the same in the new condition table (Country / Destination country / Material type / Cust tax cla / Material tax cla ). The condition table is included in the already defined access sequence. This access seuqnce is assigned to the tax conditn type ZWST.
    A condition record maintained for the conditon type ZWST for newly defined access. When I create a sales order, the ZWST condition type is not picking up the record maintained for this access. Error message  - 102 Access not made (Initialized field)
    Subsequently, thecondition value from the next access is picked up.
    Question - Did I miss any step during creation of a new field in the field catalog?
    Thanks in advance for your kind help. Be assured to get the full points if answered satisfactorily.

    Hi
    Error message - 102 Access not made (Initialized field)
    If you are getting this msg in a sales order in the analysis why a particular condition type value has not been picked
    Then this will not be a Error message and also not warning message
    There will be a yellow exclamatory mark
    Access not made (Initialized field)  conceptually means
    Suppose if you maintain a condition record say a condition type ZR00 for a sales org 1000 and DC 10 for a material X the price is Rs1000
    Now in sales order the value for ZR00 is not coming and the message is Access not made (Initialized field)
    This means that in  the sales order either sales org is not 1000 or DC is not 10
    Simply it means that condition record is maintained for sales org 1000 and DC 10 but your sales order is not created for those data
    hence the access is not executed because the initialized fields sales org 1000 and DC 10 is missing
    Hope you are getting my point
    If it is understood then you can analyze your sales order and solve your error
    Reply whether this input has been useful to you
    Regards
    Raja

  • Mid-process Receive (onEvent) is not picking up published event

    We have a composite (CompositeA), which has 2 BPEL processes (bpelprocess1 and bpelprocess2). bpelprocess1 is synchronous and bpelprocess2 is a one-way. bpelprocess1 receives a message from the client - then sends the message using a one-way Invoke action to bpelprocess2 - bpelprocess2 transforms the message and assigns some values - then sends the message to Event1 through an Invoke action - bpelprocess1 has a Receive activity waiting for an event from Event1 - then it will send the message back to the client as the Reply. Everything works up to the point where the bpelprocess1 Receive(onEvent) activity is waiting for an event, it sits in this "Pending" state until the SyncMaxWaitTime value has expired and then we get a timeout error (see below).
    "Waiting for response has timed out. The conversation id is null. Please check the process instance for detail."
    So our question is, why does the Receive(onEvent) in bpelprocess1 never pick up the published event? We've run some additional tests to ensure the event is being published, and that has been confirmed.
    Is it possible to receive an event that was published during the current instance of the process (i.e., since bpelprocess1 invoked bpelprocess2 which invoked the Event1 publish, can bpelprocess1 perform a mid-process Receive of the event that was just published?
    Please let us know if this makes sense or if you have any additional questions.
    On a side note, if we create an independent mediator component in the same composite and have it subscribe to Event1 as well, then just write the message out to a file. It would not pick up the message from the EDN in the scenario described above, if we set the property nonBlockingInvoke=true or bpel.config.transaction=requiresNew on the bpelprocess2 partnerlink from bpelprocess1, the Mediator would get the message from the EDN, but bpelprocess1 still timed out waiting for the event. If we setup another BPEL process (bpelprocess3) in the same composite (though not linked to bpelprocess1 and bpelprocess2) and it has a mid-process receive onEvent listening for Event1, it does not pick up the published event either, so seems to be an issue with the mid-process receive onEvent in the synchronous BPEL process.
    Any help is appreciated.

    Thanks for the reply, but there is no issue with the one-way from bpel1 to bpel2, we do not expect nor want a response from bpel2, it should just publish the event and complete. The bpel1 should continue it's flow (which it does) and the next action is a Receive action listening for an event (that was published by bpel2), but the Receive never finds the event.
    Here's a less complex use case:
    1. bpelprocess1 is a synchronous process which publishes to Event1 (this completes successful and returns a success message to the client)
    2. bpelprocess2 is an asynchronous process which has a mid-process Receive action that is listening for Event1
    3. bpelprocess3 is a process which is initiated by Event 1
    If we execute bpelprocess2 it will set at the mid-process Receive action in a PENDING state, waiting for Event1 to occur.
    If we then execute bpelprocess1 the Event1 is published and we receive a "SUCCESS" response back.
    At this point bpelprocess3 is initiated (b/c it's initial Receive is triggered by Event1)
    We would also expect the mid-process Receive in bpelprocess2, which is in a PENDING state to trigger, but it never does.
    Hopefully this use case makes more sense.

  • Purchase Order Carryforward Does Not Net to Zero

    We are working in a year-end test client, copy of Production, in preparation for fiscal year end closing.
    For purchase order carryforwards, we find a number of documents which do not net to zero in the sender year. This seems to occur most often for the case where a line item has split account assignments. In these cases, only one account assignment line is carried forward. The other account assignment lines are ignored.
    This does not occur for all cases where we have split assignments. We have been unable to determine what is unique about the instances where the carryforward does not work properly.
    Our system is R/3, 4.7, support stack 27.
    Has anyone else encountered this problem? If so, can you give me any guidance as to how to address it?
    Thank you.

    Hello all. Since i didn't get any replies, I don't know if there is any interest in this. However, for future reference, in case any else encounters this issue and searches the forum, here is the answer which we found:
    FMJ2 and FMJ3 process the carryforwards and reversals in blocks of 2000 lines. At the end of a block, the PO may be split up across blocks, with one or more assignment items processed in the first block, and the remaining items in the next block.
    If you have selected "Block Documents" on the initial screen, when the first item is processed, it locks the PO. When the second block attempts to process the remaining items, there is an error that the PO is locked, and these items are not processed.
    The developer is working on a correction to the code to handle this. In the meantime, there are two workarounds:
    1) Uncheck "Block Documents"
    or
    2) After processing, use FMJ3 to reverse the carryforwards which received the error. Use FMJ2 to carry them forward again, in smaller groups which are not large enough to fill up a 2000 line block, and which therefore do not encounter the problem.

  • MR11 not picking PO for clearing

    Hi,
    We are unable to clear one item of a PO through MR11. Even though the PO has GR surplus, system is not picking for clearing.
    Below are the transactions done on the PO.
    Credit memo cerated on: 13.04.2009
    MIGO created on:             24.04.2009
    MIRO created on:             24.04.2009
    In above case Credit memo is done prior to Invoice and GR. I want to know what could be the reason of MR11 not clearing the PO.
    Thanks.

    Hi,
        Please check balance of Gr/IR account  by TRC: MB5S .
       If balance is zero,  yo do not need TRC: MR11.
    Regards,
       Gaito

  • CUP- Request not picking approvers from BRF+ - 10.0

    Hi,
    We are on SP7 - GRC 10.0
    We created the BRF+ conditions with business process and given user id as the Agent condition for approver. MSMP workflow was created with the above agent.
    When we create a request it is getting successfully created but not appearing in the workinbox of Approver. We checked the Instant status and there it shows the path and the stage where it is but the Approvers column as blank.
    We used the same conditions in SP 5 and no issues were identified. After upgrade to SP7 we are facing the issue.
    Is there anything which is missed in settings?
    Thanks and Best Regards,
    Srihari.K

    Hi Nikita & Joshita,
    Further to above
    We replicated the same scenario in our sandbox environment and it worked fine. But when it comes to Dev system its not working.
    I observed the following difference in Agent Decision table from Sandbox & Dev
    Sandbox:
    Result Data Object
    - Return all matches found
    - Return an initial value if no match is found
    - Return an exception if partial match is found
    - Seggregate the result data object into its constituent elements
    1) & 4) are checked and Result Data Object : GRFN_MW_T_AGENT  [All these were taken by default]
    Dev:
    - Return all matches found
    - Return an initial value if no match is found
    - Return an exception if partial match is found
    2) is checked and Result Data OBject : Result-Agent Rule
    How these differences when both are on same SP 7. Is there any thing wrong in the above setting which needs to be corrected. Where the agent rule is not picking up the approvers ?
    Thanks and Best Regards,
    Srihari.K

  • PO Output Type not picked

    Dear Experts ,
    I have defined a new condition table for PO o/p as  Doc Type/P Org/Vendor/Plant.
    I assigned this table to the access seq
    & the acces seq to the output type .
    Then I maintained Condition record for this acces seq
    But the output tupe is not getting picked in the PO
    The analysis shows the message  Access Not Made (Initialized Field)   .
    Also I not that the system cannot pick the value of plant from the PO .
    to solve this I ticked the "Initialize" tick box in the access field WERKS.
    now the message is gone , but still the o/p type doesnt pick.
    please sugges if this is possible at all ( I have doubts as the plant is an item level field in PO ) . If yes how .
    Regards
    Anis

    Dear Anis,
    If output type is triggered with txn like ME9F, then you can get data from EKPO table itself. Otherwise you can use options.
    1. Export item data from some userexit or BADI (ME_PROCESS_PO_CUST) to memory id and then get that data in userexit userexit_komkbea_fill.
    2. Using field symbol, you can get the data in userexit userexit_komkbea_fill from memory.
    Data : W_Text(30) type C
    Fields symbols : <FS> type EKPO.
    w_text = '(Program name)EKPO[]'.
    Assign w_text to <FS> .
    Kind Regards,
    Suneet

  • Delta Extractor Is not picking changed values

    Hi All,
    When the values or texts in a PO are changed the delta extractor is picking up the changed values as deltas  (provided the changes where done in PO <b>Header</b> or <b>Item Overview</b>) but when a PO values or text that are changed in the <b>Item Details</b> the delta mechanism is not picking up the changed values (the fields whose values are changed were initially not in the LO Cockpit Extractor they where added and the values to these fields are populated using an ABAP Program)
    Is there a reason that Delta mechanism doesn't work for fields that are not delivered by the SAP Extractor or do we need to modify the code in order to collect these changed values by Delta Mechanism (Direct Delta as the Update Mode).
    Please let me know if anybody came across the same problem .
    Thank you all in advance.
    Regards,
    Dhanam

    Hi,
    this is another story.....
    You'll have to
    - enhance the PO items table (EKPO) with your fields
    - activate the right customer exit for purchase orders (search in SMOD; or in this forum..) and populate your fields during this exit. if the field needs to be maintainable by the R3 user, you'll have find a SAP exit (again SMOD) in order customize one of the screen and populate your fields in R3.
    - use another exit to populate the new fields to LO delta queue
    - enhance your BW extract structure (done)
    - and so on...
    As you can imagine, the above get quite more complicated (an expert in MM shall support you) and it needs to be approved by the PM since you'll modify R3.
    But that's basically it!
    hope this helps...
    Olivier.

  • System is not picking up approvers from BADI in Item level workflow

    Hi All,
    My problem is that
    1. when I creat the shopping cart the system is picking up the correct approver from BADI and showing it in approval preview.
    2. My first level approver is a general task so Workitem going to the correct persons.
    3. after first level approver I am fillng approver in BADI for 2 nd level.
    4. But after first approval the SC is directly getting approved finally as system is not picking up approvers from the BADI.
    I dont understand the problem. even We applied SP9 as well, but the problem is not resolved.
    Please suggest something.
    Thanks
    Smita

    Hi ,
    I am pasting the code of my BADI.  Let me know if i need to do some changes.
    Regards,
    smita
    if lv_wf = '4'.
    1st approval step executed for indices 1 and 0
          IF actual_approval_index LE 1.
    First approval step (General task)
    endif.
    2. approval step executed for indices 2,1 and 0
          IF actual_approval_index LE 2.
    *break-point.
    **get the approver for the commodity
             LOOP AT lt_item INTO ls_item WHERE del_ind IS INITIAL.
    We consider only items, which are not deleted (del_ind = 'X')
    Set the product category
                MOVE ls_item-category_id TO lv_call_value1.
    Find the approver of this item based on the customizing table ZCOMMODITY
    CALL FUNCTION 'ZWF_COMODITY_ITEM_APPROVAL_GET'
       EXPORTING
         SC_GUID                          = ls_header-guid
         ITEM_GUID                        = ls_item-guid
       APPROVAL_DESCRIPTION             =
        HIDE_ITEMS_NOT_RESPONSIBLE       = 'X'
         CRITERION1                       = 'COMMODITY'
         CATEGORY_ID                      = ls_item-category_id
         ITEM_VALUE                       = ls_item-VALUE
         APPROVAL_INDEX                   = '2'
       CHANGING
         APPROVAL_TABLE                   = approval_table
         ITEM_APPROVAL_TABLE              = item_approval_table
        ITEM_APPROVAL_OBJ                = item_approval_obj
    endloop.
    *ELSEIF actual_approval_index EQ 2.
    don't process 2nd step
             no_further_approval_needed = 'X'.
    endif.
    endif. " if lv_wf = '4'.
    FUNCTION ZWF_COMODITY_ITEM_APPROVAL_GET.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(SC_GUID) TYPE  BBP_GUID
    *"     VALUE(ITEM_GUID) TYPE  BBP_GUID
    *"     VALUE(APPROVAL_DESCRIPTION) TYPE  BBP_STEP_DESCRIPTION OPTIONAL
    *"     VALUE(HIDE_ITEMS_NOT_RESPONSIBLE) TYPE  BOOLEAN OPTIONAL
    *"     REFERENCE(CRITERION1) TYPE  BBP_WFL_APP_CRITERION
    *"     VALUE(CATEGORY_ID) TYPE  ZBBP_CATEGORY_ID
    *"     VALUE(ITEM_VALUE) TYPE  BBP_VALUE
    *"     VALUE(APPROVAL_INDEX) TYPE  SWH_NUMC10
    *"  CHANGING
    *"     REFERENCE(APPROVAL_TABLE) TYPE  BBPT_WFL_APPROVAL_TABLE_BADI
    *"     REFERENCE(ITEM_APPROVAL_TABLE) TYPE  BBPT_WFL_ITEM_APPROVAL_BADI
    *"     REFERENCE(ITEM_APPROVAL_OBJ) TYPE  BBPT_WFL_ITEM_APPROVAL_OBJ
    *"       OPTIONAL
    this Function Module is for getting the commodity approvers
    for the commodity items, in the Shopping cart
      DATA:
        ls_approval_table      TYPE bbp_wfl_approval_table_badi,
        ls_item_approval_table TYPE bbps_wfl_item_approval,
        ls_approval_def        TYPE bbpt_wfl_lia_def,
        ls_item_approval_obj   TYPE BBPS_WFL_ITEM_APPROVAL_OBJ.
      DATA:
        lv_app_obj_guid   TYPE bbp_guid_32,
        lv_is_new_approval_object TYPE boolean.
    **structure for commodity data
    data : ls_commodity type zcommodity.
    data : lv_value1 type BBP_WFL_APP_PROPERTY.
      CONSTANTS:
          c_agent_is_user TYPE otype VALUE 'US'.
    First find the right approval object the item belongs to.
    All items of an approval object are approved togheter in
    this approval step, and therefore only one workitem is
    created for this items. IF possible use this standard function
    BBP_WFL_DIN_APP_OBJ_GET for creating the approval object.
    lv_value1 = category_id.
    CALL FUNCTION 'BBP_WFL_DIN_APP_OBJ_GET'
      EXPORTING
        SC_GUID                      = sc_guid
        CRITERION1                   = criterion1
      CRITERION2                   = ''
      CRITERION3                   = ''
       VALUE1                       = lv_value1
      VALUE2                       = ''
      VALUE3                       = ''
    IMPORTING
       APPROVAL_OBJ_GUID            = lv_app_obj_guid
      IS_NEW_APPROVAL_OBJECT       =
      TABLES
        ITEM_APP_OBJ                 = item_approval_obj
                  CALL FUNCTION 'BBP_WFL_DIN_APP_OBJ_GET'
                    EXPORTING
                      SC_GUID                      = sc_guid
                      CRITERION1                   = criterion1
                     CRITERION2                   = ''
                     CRITERION3                   = ''
                     VALUE1                       = lv_value1
                     VALUE2                       = ''
                     VALUE3                       = ''
                     IV_ITEM_VALUE                = ITEM_VALUE
                   IMPORTING
                     APPROVAL_OBJ_GUID            = lv_app_obj_guid
                     IS_NEW_APPROVAL_OBJECT       =
                    TABLES
                      ITEM_APP_OBJ                 = item_approval_obj.
    CALL FUNCTION 'BBP_WFL_DIN_APP_OBJ_GET'
       EXPORTING
         sc_guid                 = sc_guid
         criterion1              = criterion1
      CRITERION2              = ''
      CRITERION3              = ''
         value1                  = category_id
      VALUE2                  = ''
      VALUE3                  = ''
      IMPORTING
    If 2 items of the same shopping cart have the same
    values for the criterias, this function returns the
    same (!!!) approval object guid
        approval_obj_guid       = lv_app_obj_guid
       TABLES
    This table saves the criterias  for which the approval object
    was created. For example:
    |approval object1| "cost center" | 1000   |
    |approval object2| "cost center" | 1200   |
    |approval object3| "prod categ " | office |
        item_app_obj            = item_approval_obj
    Check if this approval object already exists in the approval
    table
      READ TABLE approval_table INTO ls_approval_table
              WITH KEY approval_object_guid = lv_app_obj_guid
                       approval_index       = approval_index.
      IF sy-subrc EQ 4.
        lv_is_new_approval_object = 'X'.
      ENDIF.
      IF lv_is_new_approval_object = 'X'.
    Now read your own approval table based on your criteria's
    **now check whether the category id is a commodity material and
    *find the responsible person for that and
    *check if the amount of item is falling in the approval limit of the comodity manager
    select single * from zcommodity into ls_commodity
    where CATEGORY_ID = category_id
    and ( ZFROMAMT <= item_value and ZTOAMT >= item_value ).
       SELECT * FROM bbpt_wfl_lia_def
                INTO CORRESPONDING FIELDS OF ls_approval_def
                WHERE
                      app_crit_name1  = criterion1 AND
                      app_crit_value1 = value1
       ENDSELECT.
        IF sy-subrc NE 4.
    Fill approval table (who is responsible for which approval
    object in which approval step)
          ls_approval_table-approval_index       = approval_index.
         CONCATENATE c_agent_is_user ls_approval_def-approval_agent1
                                 INTO ls_approval_table-approval_agent.
    CONCATENATE c_agent_is_user ls_commodity-person
                                  INTO ls_approval_table-approval_agent.
          ls_approval_table-name = ls_commodity-name.
          ls_approval_table-approval_description = approval_description.
          ls_approval_table-approval_object_guid = lv_app_obj_guid.
          ls_approval_table-hide_items_not_responsible =
                                  hide_items_not_responsible.
          APPEND ls_approval_table TO approval_table.
         IF ls_approval_def-approval_agent2 IS NOT INITIAL.
    Second approver for the same workitem exists
           CONCATENATE c_agent_is_user ls_approval_def-approval_agent2
                               INTO ls_approval_table-approval_agent.
           ls_approval_table-name = ls_approval_def-agent_string2.
           APPEND ls_approval_table TO approval_table.
         ENDIF.
        ENDIF.
      ENDIF.
    Fill item table (Which items belongs to which approval object)
      ls_item_approval_table-approval_object_guid = lv_app_obj_guid.
      ls_item_approval_table-approval_item_guid   = item_guid.
      APPEND ls_item_approval_table TO item_approval_table.
    **Fill Item approval object
    ls_item_approval_obj-sc_guid = sc_guid.
    ls_item_approval_obj-APP_CRIT_NAME1 = CRITERION1.
    ls_item_approval_obj-APP_CRIT_VALUE1 = CATEGORY_ID.
    ls_item_approval_obj-APPROVAL_OBJECT_GUID = lv_app_obj_guid.
    append ls_item_approval_obj to ITEM_APPROVAL_OBJ.

  • Plant is not picking up in Purchase Order

    Hi all,
        I am given a fresh system to create some transactional data for R & D purpose. i have created few materials at plant level.
       while creating the purchase order the system is asking for the plant and when i give the plant the field is getting cleared off.
    checked all the assignments with other organizational elements and plant parameters as well.
    I am able to post initial stock entry for the same plant.
    What could be the reasons for not picking up the plant.
    Thanks
    Syed

    May there are some plant related mandatory condition records are maintained in your system, since you may not have maintained it, the system is not accepting the plant. Check for condition records.

  • Tax value is not picked up correctly for the condition type in SO creation

    Hi All,
    I have a issue in Picking up Tax value correctly for the condition type in SO Creation.
    Actual Issue:
    When creating the sales order manually,
    tax value is picked up correctly for one condition type: ISS3.
    When the Sales Order is created via Idoc using the function module 'idoc_input_orders', tax value is not picked for same condition type: ISS3.
    We need to find out why the value for the condition type 'ISS3' is not picked in this way!
    Can anybody solve this issue!
    What can be the reason which is stopping picking up tax value for condition type: ISS3 when Sales Order is created via F.M 'IDOC_INPUT_ORDERS'! While it picked up the same while creating Sales Order manuallly.
    Thanks in advance.
    Thanks,
    Deep.

    Hi All,
    Can anybody give the solution for above posted issue!
    Working:
    When creating the sales order manually,
    tax value is picked up correctly for the condition type ISS3.
    Actual Issue:
    When the Order is created via Idoc using the function module 'idoc_input_orders',
    tax value is not picked .
    I need to find out why the value for the condition type 'ISS3' is not picked.
    I have debugged the issue from WE19 but upto Conditions tab it is picking up tax value but then it is becoming zero again it remains zero after saving SO.
    But Manually tax value is picked up for condition type ISS3 and remains same after saving order.
    I have debugged it several times fro WE19 but not able to find route cause for the issue.
    What can be the issue over here!
    Can anybody give me solution for the same!
    Thanks in advance.
    Thanks,
    Deep.

  • Method GUI_DOWNLOAD not creating CRLF at end-of-each-line of output

    Hello SDN Community,  has anyone experienced CL_GUI_FRONTEND_SERVICES=> GUI_DOWNLOAD not putting the CRLF at end of exported lines?  This can be seen when you view the output file in notepad (the file contents wrap) or an editor with hex view enabled  (0A0D).
    I have tried running an ABAP that runs this method and on some people's laptop's the file wraps and on others the file is formatted (as would be expected) as per the CRLF's. 
    My understanding is that the GUI_DOWNLOAD method should provide the CRLF's.   And on my laptop (running Vista and SAP ECC 6.0 back-end) it wraps the output because there are no CRLF's in the file.
    Your experiences would be appreciated.
    Thank you,
    Dean Atteberry.

    Thank you, Alejandro, for your comments.  I am using two systems - on one it works and on the other it does not.
    The one that works is an SAP ECC 6.0 where the CL_GUI_FRONTEND_SERVICES class has a Last Change date of 03.07.2006.
    The one do not work is SAP ECC 6.0 where the CL_GUI_FRONTEND_SERVICES class has a Last Change date of 07/08/2009.
    If I look at the code in GET_PLATFORM, it is verry different between the two systems.
    On the one that works, it executes following code and platformID has value of '5'.  This later used to assign the correct value for CRLF variable which is used to concatenate to end of records  (value is '0A0D').
    ELSE.
    *     SAP GUI for Windows
          IF ACTIVEX IS NOT INITIAL.
    * returns Windows Platform
    * VER_PLATFORM_WIN32s             0
    * VER_PLATFORM_WIN32_WINDOWS      1       (Win95/98)
    * VER_PLATFORM_WIN32_NT           2
            CALL METHOD HANDLE->CALL_METHOD
              EXPORTING
                METHOD     = 'GetWindowsPlatform'
                P_COUNT    = 0
                QUEUE_ONLY = ' '
              IMPORTING
                RESULT     = platformID
              EXCEPTIONS
                OTHERS     = 1.
            IF SY-SUBRC <> 0.
              RAISE CNTL_ERROR.
            ENDIF.
    On the one that does not work, it executes following code.  In the debugger, when control comes back from CL_GUI_CFW=>FLUSH call, I can see the PLATFORMID variable change to '15'.  This is moved to M_PLATFORM and ultimately is used later in a case statement to assign the appropriate value to CRLF variable. 
    HOWEVER, THERE IS NO "WHEN 15" statement in the CASE statement - IT ONLY GOES UP TO '14'.   Because of this, no value is assigned to the CRLF variable and when subsequently this variable is concatenated to the output line, there is no CRLF (0A0D) at the end of the line.  Because the CRLF variable is blank.  [see coding snippets at end-of-note]
    Is there an better place than General ABAP forum to discuss this?  Possibly this item might benefit from the attention of SAP developers?
    Following are code snippets illustrating findings from debugging...
    This shows the FLUSH statement that causes '15' to appear in the PLATFORMID variable.
    IF bPLATFORMEX = ABAP_TRUE.
            CALL METHOD HANDLE->CALL_METHOD
              EXPORTING
                METHOD     = 'GetPlatformEx'
                P_COUNT    = 0
                QUEUE_ONLY = ' '
              IMPORTING
                RESULT     = PLATFORMID
              EXCEPTIONS
                OTHERS     = 1.
            CALL METHOD CL_GUI_CFW=>FLUSH
              EXCEPTIONS
                CNTL_SYSTEM_ERROR = 1
                CNTL_ERROR        = 2
                others            = 3.
            IF SY-SUBRC <> 0.
              RAISE CNTL_ERROR.
            ENDIF.
            MOVE PLATFORMID TO M_PLATFORM.
    This shows the method GET_LF_FOR_DESTINATION_GUI, where you can see that values only go up to 14.  [look in attributes for CL_GUI_FRONTEND_SERVICES to see attribute values]
    CASE PLATFORM_ID.
          WHEN CL_GUI_FRONTEND_SERVICES=>PLATFORM_WINDOWSXP.   <---- this is '14'
            MOVE CL_ABAP_CHAR_UTILITIES=>CR_LF TO GUI_CRLF.
          WHEN CL_GUI_FRONTEND_SERVICES=>PLATFORM_NT50.
            MOVE CL_ABAP_CHAR_UTILITIES=>CR_LF TO GUI_CRLF.
         <...lines snipped...>
          WHEN CL_GUI_FRONTEND_SERVICES=>PLATFORM_TRU64.
            MOVE CL_ABAP_CHAR_UTILITIES=>NEWLINE TO GUI_CRLF.
          WHEN CL_GUI_FRONTEND_SERVICES=>PLATFORM_OS2.
            MOVE CL_ABAP_CHAR_UTILITIES=>NEWLINE TO GUI_CRLF.
          WHEN CL_GUI_FRONTEND_SERVICES=>PLATFORM_UNKNOWN.
            RAISE CNTL_ERROR.
        ENDCASE.
      ENDIF.
      MOVE GUI_CRLF TO LINEFEED.
    This shows the FORM put_char_linebuffer you can see CRLF being concatenated to output line...
    prc_column_idx = prc_column_idx + 1.
        ENDWHILE.
        CONCATENATE prc_encoded_string prc_encoded_crlf
          INTO prc_encoded_string IN BYTE MODE.
      ENDIF.
    * Add data lines
      LOOP AT par_data_tab ASSIGNING <f_data_tab>.
        PERFORM put_char_linebuffer USING <f_data_tab>
                                          par_write_field_separator
                                          par_trunc_trailing_blanks
                                          par_col_select
                                          par_col_select_mask
                                          par_write_lf
                                          strDecimal
                                          strDatFormat
                                          par_dat_mode
                                          par_trunc_trailing_blanks_eol
                                    CHANGING converter
                                             prc_encoded_string.
        IF par_write_lf IS NOT INITIAL.
    *     Add CR to line.
          CONCATENATE prc_encoded_string  prc_encoded_crlf
              INTO prc_encoded_string IN BYTE MODE.
        ENDIF.
      ENDLOOP.
    * Write BOM if requested and Unicode encoding
      CLEAR prc_bom_string.

  • Specific model not picking up advertisements

    The other week I went to add the Powershell module to our Boot Images
    We encountered an error trying to do that, so we gave up, and built new boot images just to be safe.
    After doing so, and triple checking everything was exactly as had been previously, we now have one specific model of computer that won't pick up advertisements.
    We have repeatedly confirmed the computer entry is in the collection, we have removed and re-added the computer and re-added it to the collection, yet it still will not pick up the advertisement. We have done this multiple times with multiple computers of
    the same model, all with zero success.
    I give up. Hive-mind, help!

    Hello,
    Have you verified smbios UUID of these computers?
    Someone else have encountered duplicate UUID which caused PXE boot issue.
    http://social.technet.microsoft.com/Forums/en-US/7702e267-6c1a-4844-9a2b-2347137b17e3/os-deployment-task-sequence-doesnt-show-up?forum=configmanagerdeployment
    So these computers may became known computers.

Maybe you are looking for