Skip to Content
avatar image
Former Member

Output Management in S/4 HANA 1610 without using BRFplus

Can we achieve output management in S/4 HANA 1610 Billing Document Output without using BRF+?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Mar 06, 2017 at 06:56 AM

    Yes, it is possible in 1610 to deactivate the new output determination on application level and use NAST instead - read 2267376 - Billing Document Output Management

    Add comment
    10|10000 characters needed characters exceeded

    • You need to ask your system administrator to provide you with S-user access (or ask your supervisor to initiate the procedure). I guess, you could ask a colleague in your company to help you out by sending you the note PDF until you get the authorizations, but if you are working on a S/4HANA project, you will definitely need a S-user: a major part of the useful information is available through SAP notes, plus, you need to review what additional corrections need to be implemented.

    Further commenting has been locked.
  • Mar 06, 2017 at 06:57 AM

    One of the first sentences in OSS note 2228611 - Output Management in SAP S/4HANA should clear your doubts as it says "It is not mandatory to use the new output management."

    Add comment
    10|10000 characters needed characters exceeded

    • if you don't have a S-user then ask someone in your company who has one to download the note for you, or ask your supervisor to approve that you get a S-user ID yourself

      Your question was if you can achieve output determination without BRF+, The note says "Yes you can still use the old output determination" - not sure what you expect now in detail - how the old output determination is setup is explained in help.sap.com and many blogs here in the community as well as in countless answers.

    Further commenting has been locked.
  • avatar image
    Former Member
    Mar 06, 2017 at 03:09 PM

    Hi Harsh,

    Output Management in S4Hana using Decision tables of BRF+ product are getting mature month after month.

    In 1511 there was 3 application objects types to work with this NEW output management.

    Now about a month ago February with 1610 we can see available more .... much more than 3... we see the stuff growing up...

    In my personal opinion working with that, when l tried to work in 1511, there was necessary some small corrections after importing.. (some erros in the decision tables, nothing complex)

    For now in 1610. You can import perfectly with no errors for any application object. (more maturing)

    We have the release date in the name of each file, l assume we need to wait a little bit more for many of them.

    About the billing we have some limited documents to work in some specific cases. That will obligatory push you back to NAST (for this moment)

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

    l see in the future (next releases) more and more adjustments with no limitations at all to use it. And more and more application objects types involved. l think when everything be stabilized SAP may leave NAST so that may will be out of the game. (it is just my opinion).

    Thank you,

    Att Leonardo de Freitas

    Add comment
    10|10000 characters needed characters exceeded

    • I am aware of the simplification pdf - this is why for some companies it makes sense to stick to the old NAST concept, at least until they can afford to redesign their processes. It would have been nice, though, if there were plans to support additional channels out-of-the-box, because it would be easier to persuade companies to switch to the new approach, or if there were a way to switch to BRF+ not just per application, but per application/channel combination (I assume that this is quite complicated to design). Having two different technologies to co-exist has the disadvantage, that it can be confusing for end users, who need to learn and understand both options, but at least from functionality perspective (getting the advantages of BRF+ for regular printouts and e-mails, without breaking the custom processes), it could be an option.

      Explaining the new output concept to end users: the billing clerks are usually experienced in pricing and account determination, and it has been relatively easy to explain NAST by using analogies - the screen and concepts are similar. With the new output concept comes a learning curve and some resistance, which is too steep for some end users. The idea of BRF+ outputs was to simplify the maintenance for supporting the solution, but, if you consider that even some experienced consultants struggle with it, it is understandable why end users would need a really simple standard app, tailored to their knowledge, needs and authorizations, to perform some initial troubleshooting. This is a part of the 'polishing', which I meant in my post.

    Further commenting has been locked.
  • avatar image
    Former Member
    Mar 08, 2017 at 05:45 AM

    Thank You Jürgen, Veselina and Leo. My issue is resolved. Cheers..:)

    Add comment
    10|10000 characters needed characters exceeded