Automate

 View Only
Back to discussions
Expand all | Collapse all

FS00 - GL Account Creation

  • 1.  FS00 - GL Account Creation

    Posted 11-06-2018 11:39
    We have a script for GL account creation based on FS00, however if an account already exists then a message is returned which is the final message after the standard "Account x already exists for company code y":

    "Cursor field (GLACCOUNT_SCREEN_COA-KTOKS Account Group) is not enabled, or is missing from screen (SAPLGL_ACCOUNT_MASTER_MAINTAIN 2001 G/L Master Record Initial Screen)"

    Does anyone have a suggestion how to return the real error into the log?  If the account exists then the script should skip (the skip option doesn't seem to properly skip the screen)?  There is also no BAPI available that I can see.

    ------------------------------
    James Tobin
    ------------------------------


  • 2.  RE: FS00 - GL Account Creation

    Employee
    Posted 11-09-2018 10:39
    Hi James - the easiest thing to do here is to enable the error code to display and then swap the error message.  I'm assuming you're on v11 or 12, in case you haven't done this before.
    1. in the mapper click on expert mode or basic - and you'll see this option available - check it
    3. Then run the script.  You'll see the error code in the SAP messages - this is for a Plant Maintenance transaction-not FS00.  Here's an example:  E:IM-003-Equipment SK-R102233 does not exist
    4. Uncheck the Technical log info checkbox
    5. then click the Launch Dialog for the Transform messages
    6. add and use the code - typically CC-NNN and enter the first part in Message ID and Message Number and type new text
    8. Uncheck the Technical log info checkbox and re-run your script.  You'll see a new message.
    I hope this helps.

    Best Regards,
    Sigrid

    ------------------------------
    Sigrid Kok
    PSE | Winshuttle North America
    ------------------------------

    Original Message


  • 3.  RE: FS00 - GL Account Creation

    Employee
    Posted 11-09-2018 11:25
    Hi James, 
    Studio typically returns the last hard stop message encountered, and because FH-006 is returned by SAP as an information message, the script attempts to carry on. 

    I tried to replicate your scenario, and you can see that the extended log does show the message you needed (FH-006). 



    I also tried Sigrid's suggestion to show a friendly message instead of "S:00-347-Field (GLACCOUNT_SCREEN_COA-KTOKS Account Group) . SAPLGL_ACCOUNT_MASTER_MAINTAIN 2001 is not an input field". 



    Regards
    Jayasri

    ------------------------------
    Jayasri Varyani | Solutions Engineer
    Winshuttle North America
    ------------------------------

    Original Message


  • 4.  RE: FS00 - GL Account Creation

    Posted 11-13-2018 00:57
    Thank you both very much for your help, this setting is very useful.  Is there a way to suppress the initial error number (eg. "S:FH xxx") on the message?  Not too much of a problem if not but thought I would check!

    ------------------------------
    James Tobin |

    ------------------------------

    Original Message


  • 5.  RE: FS00 - GL Account Creation

    Employee
    Posted 11-13-2018 17:01
    Hi James, 
    I am assuming you turned off the flag Technical Log. It was only required so you could identify what to replace. 

    If your question was to suppress the message from SAP itself,  SAP allows you to customize the behavior of messages and change them from errors to warnings and vice versa in tcode OBA5. There are some message numbers that are allowed under application FH but not this one.  

    I would still go with turning on the extended log and letting the script error out because it is a genuine error.
    - Jayasri 


    ------------------------------

    Original Message


  • 6.  RE: FS00 - GL Account Creation

    Posted 11-13-2018 18:07
    Got it thank you for your help!

    ------------------------------
    James Tobin
    ------------------------------

    Original Message


  • 7.  RE: FS00 - GL Account Creation

    Employee
    Posted 11-13-2018 19:32
    James - the last step I shared includes unchecking the option to see the message codes - the technical log information - on the MAP tab.   You don't need it anymore, as you've identified the code and swapped the message.
    'Hope that helps,
    Sigrid

    ------------------------------
    Sigrid Kok
    PSE | Winshuttle North America
    ------------------------------

    Original Message


  • 8.  RE: FS00 - GL Account Creation

    Posted 07-23-2020 18:12
    To add onto this topic I was shown one time some time back with the support team on how to remove the text but keep my purchase order number. Dose anyone the proper code to keep the number but remove the text. The ID is 06 and Message is 017. But I do not know what needs to be in the Message text to allow the number to still come though.

    Thanks


    ------------------------------
    Benjamin Kielas | Data Lead
    Generac Power Systems, Inc. | 2625106580
    ------------------------------

    Original Message


  • 9.  RE: FS00 - GL Account Creation

    Posted 07-24-2020 07:37
    Hi Benjamin,

    if you look in SAP in trx SE91 you see for this message 2 variables. You need the second one for the number.
    Enter &2 in the message text. This should give you only the number.

    Regards.

    ------------------------------
    Jan van Asseldonk | Consultant
    CTAC | +31629078169
    ------------------------------

    Original Message


  • 10.  RE: FS00 - GL Account Creation

    Posted 07-24-2020 14:05

    This did not work for me but maybe due to my understanding.




    Original Message


  • 11.  RE: FS00 - GL Account Creation

    Employee
    Posted 08-05-2020 15:22
    Hi Jan

    That's a very neat trick.  

    For anyone else wanting to try this, I found that you can enter the values, message "codes",  into SE16N for table T100 for my inputs  were 
     
    You'll see the message you would get
    So for me using ME21N the first & (or &1) is the type of document - for me "Standard PO" and the second & (or &2) is the document number.

    Here's what I saw before (with the message codes turned on):

    I changed the message for 06-017 to be &2
    Now I see only the document number as the result:
    Hope that helps you Benjamin - and anyone else.

    Thanks,
    Sigrid

    ------------------------------
    Sigrid Kok
    PSE | Winshuttle NA
    ------------------------------

    Original Message