Automating OB52 - Opening and closing of the Posting Period

[Former Member]

We would like to schedule the Opening and closing of the Posting Period using Batch Jobs, which shall be run on last day of the month in background.

That is we are trying to automate the OB52 transaction (without using Schedule Manager)

Does anyone know;

1. Whether it can be done in background

2. Which program gets triggered when we execute OB52 (se93 does not help here)

3. What is the Best Practice in Opening and closing of the Posting Period

[bond007zn]

Thanks Manoj

I really don’t know which link or which team can help on accounting system interface to SAP HANA S4 vet. 1709. Can you please share more info.

[former_member698447]

you can simply try in below link, To ask for your query

https://answers.sap.com/tags/73554900100800000266

[bond007zn]

Thanks Manoj - very helpful in this matter.

I have another query but not sure how to address this..

we are using S4HANA vers.1709 and I am planning on W automating the “Manage recurring journal” entries. Currently it’s not possible as posting schedule is “greyed out” and not available for this version in fiori.
Wondering if FBDI can be used as an alternative on Fiori launchpad, in addition, do you think if FBDI does work on fiori launchpad - any upgrade in SAP in future will not be possible.

... anyways with version 1709 what is you proposal to automate recurring journal /monthly postings from the system instead it be done manually by user?

[former_member698447]

Hi Hoosen,

Its recommended that for different query, please ask in different Question

[bond007zn]

Hi Manoj

did you mean if today is the 29 of Jan - then run the payment proposal today and there will be no impact on open close periods for payments set for 01 Feb (as an example)

Just trying to work out the best option so no failed/ impacts on payments schedules.

[former_member698447]

Hi Hoosen,

For the above example you said two days when you calculate from 29th Jan it will be 31st Jan not Feb 1st 🙂

And with the same example only Proposal does not save any periods and moreover with the same example if you are running the payment run on Feb 1st before closing the period then its fine(Jan Period Close)

Suppose if you close the January period and then if you are trying to run the payment run since you already ran the proposal so i can run the payment run on after two days then its not possible.

Hope it clears

Best Regards,

Repakula Manoj

[bond007zn]

I have automated Open/ close period but I have a question : Dies open/ close period affect the payment schedule in F110 at all for example if a period is closed in the first of the month and I ran a payment report 2 days before - will it affect payments if the period is closed.

[former_member698447]

Hi Hoosen,

Two Days before if you run the payment then no issue at all.

[Former Member]

This message was moderated.

[Former Member]

Hello,

You should use standard programs RFPERIOD_OPEN and RFPERIOD_CLOSE.

Cheers.

[former_member620129]

Hello,

Actually since lhe last october, SAP has provided us a note to allow the automatization of the OB52:

Note 1483900 - RFOB5200: Maintaining T001B in the background

Where before, we were obliged to handle that using specific pg.

Hope this helps, even not more u, but others.

Cdly

Soraya

[Former Member]

Thanks for Sharing

[Former Member]

just update t001b for the positng period variant assigned to your company code in t001 by your custom program. In this case you can incorporate any logic to prevent incorrect execution, log changes,...

[Former Member]

Hi,

Can this OB52 maintenance done ( automatic or manual ) without changing the client settings in production client ?

[Former Member]

Manimaran,

There is an SAP note which explains how to do it in Production; Search and you will find the relavant note. Basically what you need to do it use T Code SBOT look for object V_T001B make sure the checkbox current settings is selected. Do an F1 to get more information.

Hope this Helps

Good Luck

[Former Member]

Hi,

1. You can schedule jobs every month to open/close periods

2. We developed a custom program to open/close periods and we have scheduled the program as background job for an year.

3. You need to chalk out a Reporting Deadlines based on the clients business for each of the Account Type is SAP. Accounts Types D-AR; K-AP; A-Asset; M-Material; & finally S-GL. AR/AP might close immediately, GL may need to close at the last. It depends on the business and clients reporting calendar.

Hope this clarifies.

[rahulpetkar1998]

You can use this simple ABAP program. And set monthly job for this program your period will automatically opens for new month.

REPORT z_auto_open_period.

DATA: lv_bukrs TYPE bukrs, " Company Code
lv_gjahr TYPE gjahr, " Fiscal Year
lv_monat TYPE monat, " Period (Month)
lv_new_period TYPE monat, " New Period
lt_t001b TYPE TABLE OF t001b, " Table for posting periods
ls_t001b TYPE t001b, " Structure for posting periods
lv_tope1 TYPE monat, " From Period
lv_tope2 TYPE monat. " To Period.

DATA: lt_bukrs TYPE TABLE OF bukrs WITH DEFAULT KEY,
lt_mkoar TYPE TABLE OF t001b-mkoar WITH DEFAULT KEY. " Account Types

DATA: lt_result TYPE TABLE OF t001b, " To hold results for ALV
ls_result TYPE t001b. " Structure for ALV display

APPEND '1000' TO lt_bukrs. " Company Code 1000
APPEND '2000' TO lt_bukrs. " Company Code 2000

* Add all account types that need to be updated
APPEND '+' TO lt_mkoar. " Valid for all account types
APPEND 'A' TO lt_mkoar. " Assets
APPEND 'C' TO lt_mkoar. " CO-PA: Profitability Analysis
APPEND 'D' TO lt_mkoar. " Customers
APPEND 'G' TO lt_mkoar. " Special Purpose Ledger
APPEND 'K' TO lt_mkoar. " Vendors
APPEND 'M' TO lt_mkoar. " Materials
APPEND 'S' TO lt_mkoar. " G/L accounts
APPEND 'V' TO lt_mkoar. " Contract accounts

* Define current fiscal year and period (example: Period 06 for Fiscal Year 2024)
lv_gjahr = '2024'. " Financial year 2024
lv_monat = '06'. " Current period is 06

* Increment the period to open the next one
lv_new_period = lv_monat + 1.

IF lv_new_period > 12.
lv_new_period = 1.
lv_gjahr = lv_gjahr + 1.
ENDIF.

* Process each company code in the list
LOOP AT lt_bukrs INTO lv_bukrs.

* For each company code, loop through all account types
LOOP AT lt_mkoar INTO DATA(lv_mkoar).

" Get the current posting period settings for the company code and account type
SELECT SINGLE * FROM t001b INTO ls_t001b
WHERE bukrs = lv_bukrs
AND mkoar = lv_mkoar.

IF sy-subrc = 0.
" Prepare new data for updating the posting periods
ls_t001b-tope1 = lv_monat. " Update 'From period'
ls_t001b-tope2 = lv_new_period. " Update 'To period'

" Update the T001B table with the new period for the specific account type
MODIFY t001b FROM ls_t001b.
IF sy-subrc = 0.
" Save the result for ALV display
MOVE-CORRESPONDING ls_t001b TO ls_result.
APPEND ls_result TO lt_result.
COMMIT WORK.
ELSE.
WRITE: / 'Error occurred while updating for Company:', lv_bukrs, 'Account Type:', lv_mkoar.
ENDIF.

ELSE.
WRITE: / 'Posting period not found for Company:', lv_bukrs, 'Account Type:', lv_mkoar.
ENDIF.

ENDLOOP.

ENDLOOP.

* ALV Display
DATA: lo_alv TYPE REF TO cl_gui_alv_grid,
lo_container TYPE REF TO cl_gui_custom_container,
lt_fieldcat TYPE lvc_t_fcat,
ls_fieldcat TYPE lvc_s_fcat.

* Create a custom container for the ALV display
CREATE OBJECT lo_container
EXPORTING
container_name = 'ALV_CONTAINER'.

* Create ALV grid
CREATE OBJECT lo_alv
EXPORTING
i_parent = lo_container.

* Define field catalog for ALV
CLEAR ls_fieldcat.
ls_fieldcat-fieldname = 'BUKRS'.
ls_fieldcat-scrtext_s = 'Company Code'.
APPEND ls_fieldcat TO lt_fieldcat.

CLEAR ls_fieldcat.
ls_fieldcat-fieldname = 'MKOAR'.
ls_fieldcat-scrtext_s = 'Account Type'.
APPEND ls_fieldcat TO lt_fieldcat.

CLEAR ls_fieldcat.
ls_fieldcat-fieldname = 'TOPE1'.
ls_fieldcat-scrtext_s = 'From Period'.
APPEND ls_fieldcat TO lt_fieldcat.

CLEAR ls_fieldcat.
ls_fieldcat-fieldname = 'TOPE2'.
ls_fieldcat-scrtext_s = 'To Period'.
APPEND ls_fieldcat TO lt_fieldcat.

* Set data for ALV display
CALL METHOD lo_alv->set_table_for_first_display
EXPORTING
i_structure_name = 'T001B'
CHANGING
it_outtab = lt_result
it_fieldcatalog = lt_fieldcat. " Corrected parameter handling

* Show the ALV display
CALL METHOD lo_alv->refresh_table_display.