Skip to Content
avatar image
Former Member

Personas: Tcode FB50 ,Document Number Not visible After Save ..


We recently did a small personalization on transaction FB50 by hiding 'Details Tab', taking the necessary information from Details Tab and merged with 'Basic Tab'. In normal 'Default' SAP flavor, When we create a document and save ,we can see the document number posted message in the status bar, but when we create a document using our created flavor 'after save', it immediately prompts a message saying 'Put valid date' instead of a document number created message. Please let me know If I need to something to avoid this validation message after save.Thanks

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 16, 2017 at 01:51 AM

    Looks like you have some tab merging going on, and this is the consequence of how tab merging works, because it clicks on each merged tab. Since the document saving cleared out the required fields, going from one tab to another will result in the required field check kicking in. So somehow the required fields must be populated before the tab merging happens.

    To be honest, looking at the flavor, I'm not sure what's the point in merging tabs because I don't see anything from a different tab than 'Basic Data', so the result could be achieved without tab merging.... but anyway.

    To get around the problem, you could try replacing the standard Save button with a script button that looks the same but performs the following:

    • Grabs the required fields (like Document date and Posting date) from the screen and stores them in variables
    • Clicks on the standard Save button
    • Grabs the resulting 'Document xxx saved' message text from the status bar
    var message = session.findById("wnd[0]/sbar").text;
    • Populates the Document date and Posting date fields with the saved dates
    • Displays the success message using
    session.findById("wnd[0]/sbar").setMessage(message, "S");

    This may or may not work... didn't try it with this transaction but a trick like this worked with a different transaction.

    Add comment
    10|10000 characters needed characters exceeded