PGI error related to Posting Period issue

While delivering, when I do the PGI, it is not allowing ...it says "Posting only possible in periods 2009/02 and 2009/01 in company code 0430"... I closed earler posting periods using Tcode MMPV and opened the current period and fiscal in SPRO IMG. But still PGI is not allowed ...it still says "Posting only possible in periods 2009/07 and 2009/06 in company code 0430". Apart from closing earlier posting periods using MMPV and opening current fiscal in SPRO IMG, what else I need to do to overcome this PGI issue ?

Hello,
Please compare the posting periods from MMPV and MMRV
The posting period for your company in MMRV will show the exact postings periods for your company.
If this posting periods are not at par to MMPV you have to maintain it.
regards,
santosh

Similar Messages

Error "Non-permitted posting period 013"

Hi expert
When I try to load the data with datasource 3EC_CS_1A, I get the error "Non-permitted posting period 013".
This Datasource request input Fiscal Year/Period before load data, I input Fiscal Year/Period from 2000001 to 2011012 and get above error.
If I input fiscal Year/Period from 2000001 to 2010012, datasource load OK
I checked datasource in ERP (TCODE RSA3) with Fiscal Year/Period from 2000001 to 2011012 is datasource have 90 records (sucessfull)
I don't know why datasource has loaded fail with Fiscal Year/Period from 2011 to now.
I checked in OB29, Fiscal Year Variant config for Period from 001 to 016.
Please help me solve this problem.
Thanks

Hi
Follow this ... hope your error will be solved.
Go to Rsa1 in BI -
> Source system -
> select the source system and right click -
> Transfer Global Settings -
> then select Fiscal Year Varients and execute.
now the changes made in your source system will be added to your system.
after that refresh the system and start loading the data. hope your error will be solved.
santosh

Error message while posting goods issue.

Hi,
Please help me with the following problem..
I have created Sales Order, Delivery & also created the Transfer Order number. After creating Transfer ordering, while submitting post goods issue, when I click on PGI, I get
"Posting only available for period 2002/10 to 2002/11"...
As a resulf of the above, I am not able to complete Billing for all the sales orders I have created.
Can somebody please help me with above?
Regards
Nadeem

Use the MMPV transaction to check your current period. Since you have transactions already done you need to do closing for every month.
If you are on an IDES system for training purposes you can do a fast transaction by removing the plant assignment from the company code. The use the MMPI transaction to set your current period. Remmber April is period 1 if you are are using the indian financial year and fiscal year variant k4.
Then reassign the plant and now try posting It will allow you. But a word of caution. Never attempt to remove the plant asignment in the development system. It might cause errors. for that there is a separate note.
regards
Jude

Related to posting periods

while i am doing pgi in vl01n i am getting the error like posting only possible in periods 2010/12 and 2010/11 in company code 777 what i do pls help me

Hi,
Please go to transaction MMPV and open the posting period for the current period from MM side.
Also check in from FI side -
>Maintain the open and close posting period with OB52.
Hope this will help you to resolve your issue
Regards,
Krishna O

Posting periods issue though I updated in MMPV

Hi experts,
I created scheduline agreement and trying to do the PGI , system thrown an error saying 'posting periods possible only 9/2009 and 8/2009'. after this I closed the periods till sep09 in T.code MMPV, still the same error. is there anything else that I have to configure or check to resolve this issue. your help is neede.
Thanks,
Kanna.

Hi,
This is how you need to do it.
Go to Tx: OMSY or MMRV & check the current period against your company code.
Theory behind Posting Periods in SAP
Posting periods are calculated using a Config: Setting called u201CFiscal Year Variantu201D attached to the Company code. u201CFiscal Year Variantu201D is the deciding factor for the company code, whether to follow the calendar year or any other calculation method.
Eg: Fiscal year can be start from July & goes to the next year June for some companies.
Therefore what you see in the OMSY might not be the actual calendar month that SAP is referring.
(Eg: 01 means Jan, 02 means Feb, 03 means March, etc is not always the case)
So first you have to check the Fiscal Year attached to your company code.
Go to below path to check Fiscal Year attached to your company code.
IMG -> Financial Accounting (New) -> FinanciaI Accounting Basic Settings (New) -> GIobaI Parameters for Company Code -> Enter GIobaI Parameters ->
Go in to your company & Check the Fiscal Year Variant field. There you can identify whether it equals to the calendar year or not. If its not clear, take that Fiscal year variant 7 go to below IMG path;
IMG -> Financial Accounting (New) -> FinanciaI Accounting Basic Settings (New) -> Ledgers -> FiscaI Year and Posting Periods -> Maintain FiscaI Year Variant (Maintain Shortened Fisc. Year)
Go in to the node.
Select the Fiscal year & double click on Periods node.
If Fiscal Year is same as calendar year, then you should have that u201CCalendar Yru201D tick box ticked.
Now check what's the SAP Fiscal month relevant to your calendar month.
The go to MMPV & open that relevant Fiscal month accordingly.
Then you should be able to post.
Hope this helps you !
Best regards,
Anupa

Posting period issue while deleting a confirmation posted for a limit PO

Hi ..
I am facing an issue whiel deleting a confirmation posted for a limit PO.
Confirmation was posted for a limit PO in SRM and it created a service entry sheet in SAP. If I deleted that confirmation in the same posting period, then it is getting deleted. No issue here.
But if I deleted that confirmation in the next posting period then the reversal document is going to error in process. RZ20 is showing the error "Positng only possible in periods 2012/2 and 2012/3".
Posting date of reversal document is current date only and the backend posting period is 2012/3, but still it is failing with this posting period error.
If I tried to delete a confirmation posted for a normal PO then I could able to delete it even in next posting period by just changing the posting date.
Why this posting occurs while deleting the limit confirmation, even through the posting date is falls within the backenn posting periiod? Is it like, SAP system is trying to delete the service entry sheet in original posting period? Kindly help.
I am in SRM 5.0 (server 5.5) SP12.
Thanks,
Arun

OK.
Well, if the variable is not used in any interval selection, then I would say "something happened to it".
I would make a copy of the query and run it to check if I get the same problem with period 12.
   -> If not, something is wrong in the original query (you can proceed as below, if changes to original are permitted).
If so, then try removing the variable completely from the query and hardcode restriction to 12.
   -> If problem still persists, I would have to do some thinking.
If problem is gone, then add the variable again. Check.
   -> If problem is back, then the variable "is sick". Only quick thing to do, is to build an identical variable and use that one.
If problem also happens with the new variable, then it's time to share this experience with someone else and consider raising an OSS.
Good luck!
Jacob
P.S: what fisc year variant are you using?
Edited by: Jacob Jansen on Jan 25, 2010 8:36 PM

PGI -Baych deficit qty-Posting period

Dear Mates,
i have following clarifications.Iam migration the datas for January2009 i this month.I have kept my period as current period as Febraury,2009 & previous period as January,2009. I used to get following error "Deficit Qty in BA in plant material XXXXX".But when i check the stock as on PGI date i have enough stock
Now i have changed the posting period as current period as January,2009 & Previous period as December,2008.Now iam facing with such error.
Could anybody please explain the logic behind this & how system behaves & check the stock during PGI so that in my earlier setting i used to get the error and when changed the posting period i am not getting the error.
Please explain

But when i check the stock as on PGI date i have enough stock
Where you have checked ?? MB5B ?? In MMBE you could have seen the stock is available but may be the stock would have been made in some other period.
thanks
G. Lakshmipathi

Error in Opening Posting Period in MM

Dear Gurus,
I am facign an error when i am opening a posting period in MM. In MMPV, when i open the Period and execute system displays the following error message:
Client 300
Period Entered : 112009
Log
ABEND
MMPV_Date_Check Error Occured (See note 1082841)
Transaction MMPV (period closing program) cannot be executed . For more infomation see note 1082841.
Kindly provide me with the solution .
thanks in advance....

Below is straight from the OSS note. You need to set the parameter id MMPV_READ_NOTE to current date for yourself or change the number of days in CKMLMVADMIN-KDATA to 999 (for example) and then you will be able to do. Probably better to set the parameter id for yourself and suitable colleagues only:
This note provides a feature to prevent using MMPV to shift into a future period. This feature is activated automatically after implementing this note and works with our without Material Ledger active. MMPV can continue only if the new period is within 10 days (by default but is configurable) away from the current date in the system. Otherwise, it will terminate and no change will be made.
To disable this feature, you must set parameter ID MMPV_READ_NOTE with the current date in the user parameters in form YYYYMMDD (Y = year, M = month, D = day).
To change the number of days to a value other than the default (10 days), set the following entry in table CKMLMVADMIN:
KKEY : MMPV_NUMBER_DAYS_ALLOWED
KDATA : <number of days MMPV is allowed>
Only integers are allowed, with 0 meaning MMPV is allowed only on or after the first day of a new period. If the value is greater than the actual number of days in a period then it means MMPV is allowed for the entire month. Any invalid entry in the KDATA field will be ignored and the default value will be used.
Regards,
Nick

Posting period issue for company code

Hi,
I am getting problem like posting period is not possible in certain duration for particular company code.
So, what is the path in SPRO to make configuration changes for this issue.
Thanks in Advance ...
Sridhar.

Dear Go to OB52 there change your configuration as I given below..   enjoy
0001     +                                   1     2008     12     2009     13     2008     16     2009
0001     A                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010
0001     D                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010
0001     K                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010
0001     M                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010
0001     S                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010
0002     +                                   1     2000     12     2010     13     2000     16     2010
V001     +                                   1     2000     12     2010     13     2000     16     2010

Posting period issue

Hi People,
I recently made some new company code config in my ides. When I did MB1C it gave me usual message which comes for opening posting period but the problem is that the message was of next fiscal year. I would give an example.
Lets take todays date that is 02/03/2010. When i did MB1C, it should give me an message as posting only possible in period 2009/11 and 2009/10 . But instead of it the message is posting only possible in period 2010/11 and 2010/10. It is taking posting period of 2010 instead of 2009. Accordingly it is allowing me to do posting in 02/01/2011 as it is 11th period of 2010 which is open, although it get a warning message of posting in the future.
I have used fiscal year variant as V3( march to april). In other company codes there is no such problem. Please guide what the issue could be.
Thanks

Hi
Go to OMSY
enter the company code :
Enter the year 2010 month 03
save
go to MMRV enter the company code check the period will be 03 2010
You can do the MB1c transaction
But every month end you should close the previous month and open the next month
Regards
G.Ganesh Kumar

Posting Period Issue Production

Hi All,
Someone at the client Closed Sept and Oct 2008 in MMPV and now , postings cannot be made to Aug 2008.
in MMRV, it shows current preiod ad Oct 2008 and prev period as Sept 2008.
How can I fix this in such a way that users can post to August again?
Appreciate any quck response.
Thanks in advance

Reopen The Closed Period
It is possible to re-open a previously closed period. However, it is NOT advisable to do so because the valuation data of the previous period could be affected.
In general, it is only safe to reopen a previously closed period when no material postings have been done after the period shifting to the new period.
If there has already been postings after the period shifting to the new period, reverting the period back will cause database inconsistencies in the history tables.
If you decide to proceed with this process, you can use the program RMMMINIT, but, please review the documentation of this program first!! and the check the SAP notes 487381 (for the error message that you are receiving) and the 369637 (for an explanation about the inconsistencies that will be generated.
Steps are as below;
Go to Transaction Code SE38
Enter program name RMMMINIT
Execute or press F8 function button
Enter your company code (From and To)
Enter relevant date: Say 01/03/2008 for Mar. 2008 month to be opened as of now
That means, user can post for the month of Feb 2008 as well as Mar. 2008
Refer SAP Note No. 487381 for more details.
As per SAP Notes 487381 ( If the periods are opened in advance in mmpv to again change it to current period the following process should be follow ), Go to Tcode MMPI, then go to menu bar and select system -> user profile->owndata.In that screen , under the parameters tab enter MMPI_READ_NOTE in Parameter ID field and enter, then under short description you will get Initialise period. Next Save.
Again go to MMPI enter company code, period and year and execute.
XXXXXXXXXXXXXXXXXX
Other way of doing it is follow these steps( But try this method in Sand box Only):
1. Go to OX18, and delete the plants assigned to your CO.Cd and save.
2. Go to OMSY and change the posting period to the one u want and save.
3.Go to OX18 and assign the plants you have deleted in step 1.and save.

MM posting period issue

Dear All,
We are closing Period in MM by 25th of every month for some reporting purpose. But we did not select ABP(Allow Back Posting).
But for some cases, we need to post the material documents from 25th to month end. But for these documents, there will not be any value update, only Qty update.
Please advice.
Sateesh

i think, becoz of ur posting period, value n quantity updation will not get affect.
now, tell me, that material is valuated material, if yes, then check that for this material type under ur valuation area, qty and value updation are ticked or not.
spro -> LG -> Materail master -> Material types -> Define Attributes of Material Types -> here select ur material type.
thanks.
Edited by: Ms. nisha on Jun 2, 2011 8:49 AM

Error :in opening posting period

For opening posting period April08-March 09 what to do?
Posting varient is created for current posting period,now for new posting period is it so to create new varient ?
& if new varient created then how to assign to company code as one current varient already assigned

You can have the same posting period variant.
Go to Tcode OB52 and give your open period and close period for normal posting periods
as well as
for special posting periods.
Cheers!

Issue relating to posting period

Hi Gurus,
we have an issue that the normal users also able to post the special periods.
from per 1 to To per 1 are belongs to authoriztion group
AAA and (special users )
from per 2 to To Per 2 are belongs to authorization group BBB which are normal users.But these users are able to post the special periods also.
can we specify any where or map the interval ( From per 1 to TO period 1 to the authorization field ie the particular interval to be valid for the authorization specified)
thanks in advance.

Hi,
I have increased my heap size to 8GB ,but still getting the same error.
the error is **Can't call method getObjectNames on class com.waveset.ui.FormUtil ==> java.lang.OutOfMemoryError: **
I'am not able to find FormUtil in my war file somehow i foound the file is html file from my local war but even if i try making changes in the file i cant change the menthod getObjectNames as it is a default method...
please suggest the solution
Thanks

Error While Doing Post Goods Issue

Hi SD Gurus
While I am Doing PGI for Standard Order, I am Getting the following Error.
Version : 5.0
Clien: 800
Runtime Errors         PXA_NO_FREE_SPACE
Date and Time          24.01.2008 23:50:48
Short dump has not been completely stored (too big)
ShrtText
No PXA storage space available at the moment.
What happened?
The current ABAP/4 program had to be terminated because there
was no space available to load it.
Each ABAP/4 program to be executed is stored in a central
storage area that is divided between all users.
This area was too small to hold all currently active programs for all
users.
The current program, "SAPLMCB1", had to be terminated because a capacity limit
has been reached.
What can you do?
Since this could have resulted in a temporary bottleneck, you should
try to restart the program.
Ask your system administrator to increase the size of the area (PXA)
used to store the ABAP/4 programs.
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
Unable to load a program of 1234944 bytes.
The PXA ('program execution area') was too small to hold all
currently active programs for all users.
At present, the size of the PXA is set at 145444 Kbytes.
How to correct the error
The current size of the PXA was set at 145444 kilobytes.
You can increase or decrease the PXA in the SAP profile. When
doing this, please refer to the relevent instructions in the
installation manual.
You can use the utility program 'ipclimits' to display the
available system resources.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"PXA_NO_FREE_SPACE" C
"SAPLMCB1" or " "
"LIS_VERBUCHUNG"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "super"
Network address.......... "192.168.0.10"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "Intel 801586 (M"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "SUPER"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPPRD"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Apr 18 2004 23:27:50"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "10"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8112
EM....................... 11498256
Heap..................... 0
Page..................... 65536
MM Used.................. 7861472
MM Free.................. 498776
SAP Release.............. "640"
User and Transaction
Client.............. 800
User................ "SAPUSER"
Language key........ "E"
Transaction......... "VL02N "
Program............. "SAPLMCB1"
Screen.............. "SAPMV50A 4004"
Screen line......... 26
Information on where terminated
The termination occurred in the ABAP program "SAPLMCB1" in "LIS_VERBUCHUNG".
The main program was "SAPMV50A ".
The termination occurred in line 0 of the source code of the (Include)
program " "
of the source code of program " " (when calling the editor 00).
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
E0
SY-UCOMM
WABU_T
SY-TITLE
Change Outbound Delivery
SY-MSGTY
E
SY-MSGID
WMOD
SY-MSGNO
081
SY-MSGV1
M1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
15 FORM         SAPLMCB1                            LMCB1F20                              200
LIS_VERBUCHUNG
14 FORM         SAPLMCB1                            LMCB1F20                              198
LIS_VERBUCHUNG
13 FUNCTION     SAPLMCB1                            LMCB1U03                               57
MCB_STATISTICS_LIS
12 FORM         SAPMM07M                            MM07MFB9_BUCHEN_AUSFUEHREN            863
BUCHEN_AUSFUEHREN
11 FUNCTION     SAPLMBWL                            LMBWLU17                                6
MB_CREATE_MATERIAL_DOCUMENT_UT
10 FUNCTION     SAPLMBWL                            LMBWLU21                               45
MB_POST_GOODS_MOVEMENT
9 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                599
BELEG_SICHERN_POST
8 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                 64
BELEG_SICHERN_01
7 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                 14
BELEG_SICHERN
6 FORM         SAPMV50A                            MV50AF0F_FCODE_SICH_OHNE_CHECK         10
FCODE_SICH_OHNE_CHECK
5 FORM         SAPMV50A                            MV50AF0F_FCODE_WABU_VL02               10
FCODE_WABU_VL02
4 FORM         SAPLV00F                            LV00FF0F                               92
FCODE_BEARBEITEN
3 FUNCTION     SAPLV00F                            LV00FU03                               45
SCREEN_SEQUENCE_CONTROL_INIT
2 FORM         SAPMV50A                            MV50AF0F_FCODE_ANFORDERUNG             33
FCODE_ANFORDERUNG
1 MODULE (PAI) SAPMV50A                            MV50AI0F                               66
FCODE_ANFORDERUNG
Chosen variables
Name
Val.
No.      15 Ty.          FORM
Name LIS_VERBUCHUNG
RSJOBINFO
00000000000000                                  ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
CON_ZEITP
BF
44
26
XMCMSEG[]
Table IT_895[1x2708]
4D947FA400005000700000009000FFFF0000A4000000C380
85F283F200001100F30010004A00FFFF4E20812040001000
XMCBEST[]
Table IT_894[2x1059]
13943FA400005000700000002000FFFF000094000000C380
8FD283F200000100E30020003400FFFF4E20852080009000
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
0
0000
0000
%_VB_SWITCH_KEY
2222222222222222222222222222222222
0000000000000000000000000000000000
I_MSEG-BNBTR
0000000
000000C
FLG_BW
X
5
8
MSPR
00000000000000 #######################################
2222222222222222222222222222222222222222333333333333332000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000C000000C000000C000000C000000C0000
CON_MODUS_SIM_NEW
F
4
6
%_DUMMY$$
2222
0000
IF_RELEASE
1
0000
1000
H_E1CMCCO[]
Table[initial]
0000FFFF
0000FFFF
SY-REPID
SAPLMCB1
5454444322222222222222222222222222222222
310CD32100000000000000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
TMCW
00
222223322222222222222222222
000000000000000000000000000
HLP_CONTROL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
S035
0000000000        ########################
2222222222222222222222222222222222222222222222333333333322222222000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000C0000000C0000000C
No.      14 Ty.          FORM
Name LIS_VERBUCHUNG
IF_RELEASE
1
0000
1000
No.      13 Ty.          FUNCTION
Name MCB_STATISTICS_LIS
MSLB
000000 ############################
2222222222222222222222222222222222222222222222333333200000000000000000000000000002222222222222
00000000000000000000000000000000000000000000000000000000000C000000C000000C000000C0000000000000
I_MODUS
2
0
CON_MODUS_LOG
C
4
3
IDOC_SENDEN
2
0
TRUE
X
5
8
SYST-REPID
SAPLMCB1
5454444322222222222222222222222222222222
310CD32100000000000000000000000000000000
T001K
     0000
2222222222222222222222222222220002222223333
00000000000000000000000000000000C0000000000
LIS_UPD
X
5
8
EKPO
00000 00000000
2222222222222333332233333333222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_MSEG-PS_PSP_PNR
00000000
33333333
00000000
MKPF
0000      00000000000000000000000000000000000000
2222222222222333322222233333333333333333333333333333333333333222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
No.      12 Ty.          FORM
Name BUCHEN_AUSFUEHREN
SY-REPID
SAPMM07M
5454433422222222222222222222222222222222
310DD07D00000000000000000000000000000000
%_VB_SWITCH_KEY
2222222222222222222222222222222222
0000000000000000000000000000000000
RSJOBINFO
00000000000000                                  ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
WS_MENG_WA
0000000222
000000C000
XMKPF[]
Table IT_532[1x205]
4A940D940000400010000000C000FFFF0000ED001000C380
83A281F20000610042001000D000FFFF4E20050000001000
KZDWS
1
3
1
XMSEG[]
Table IT_492[1x1241]
1B74598400002000E0000000D000FFFF00005D000000C380
0FA283C200000100C10010009400FFFF4E20060080001040
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
0
0000
0000
SYST
0000000000000000000000000000000000000000000000000000000000008000000000000000200000000000000000
0000000010000000000000000000000000000000100000001000000010004000000000000000A00000000000000000
T003M
800WL02
3335433
8007C02
XMCMSEG[]
Table IT_895[1x2708]
4D947FA400005000700000009000FFFF0000A4000000C380
85F283F200001100F30010004A00FFFF4E20812040001000
XMCMSEG
800M1                SCCLSCCL                    0000000111EA INR -
3334322222222222222225444544422222222222222222222333333333344244522222222222222222222222222222
800D10000000000000000333C333C0000000000000000000000000001115109E200D00000000000000000000000000
XEKLB
00000000          000000000          0000                         ##############     0000#####
3333333322222222223333333332222222222333322222222222222222222222220000000000000022222333300000
000000000000000000000000000000000000000000000000000000000000000000000000C000000C00000000000000
T333T
000
22222223332222222222222222222222222
00000000000000000000000000000000000
ZMSEG-MAT_PSPNR
00000000
33333333
00000000
XPF02
2
0
XMCBEST[]
Table IT_894[2x1059]
13943FA400005000700000002000FFFF000094000000C380
8FD283F200000100E30020003400FFFF4E20852080009000
XPAUS
2
0
XMCMRES[]
Table IT_1030[0x129]
00005FA400000000000000008000FFFF000024001000C380
000083F20000D200640000001000FFFF4E20072000001000
XBCODE
2
0
KZDCH
1
3
1
T000
800IDES-ALE: Central FI SystFrankfurt - Deutschland EUR            C1     X I802358     20041
3334445244432466776624425777476666777222467776666662245522222222222243222225243333332222233333
8009453D1C5A035E421C06903934621EB65240D04554338C1E40055200000000000031000008098023580000020041
No.      11 Ty.          FUNCTION
Name MB_CREATE_MATERIAL_DOCUMENT_UT
RBDTER
0000000000000000
2223333333333333333
0000000000000000000
RIDNLF
2222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000
KZBWA
01020304050607B3SZK3
33333333333333435543
01020304050607233AB3
FUSS-UPVOR
2
0
UPTYP_LG
3
3
3
%_SPACE
2
0
MLGVM07I-DISPO
YTFMAT
222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
FUSS-UPTYP
2
0
SYST-REPID
SAPLMBWL
5454445422222222222222222222222222222222
310CD27C00000000000000000000000000000000
MVM07I-LFGJA
FUSS[]
Table IT_377[0x4488]
000000000000D000700000008100FFFF00001E000000C380
0000000000005000910000008100FFFF40200D0020001000
ECODE
NP
45222222222222222222
E0000000000000000000
CCODE_NEXT
22222222222222222222
00000000000000000000
FCODE
NP
45222222222222222222
E0000000000000000000
FCODE_NEXT
NP
45222222222222222222
E0000000000000000000
PCODE
22222222222222222222
00000000000000000000
No.      10 Ty.          FUNCTION
Name MB_POST_GOODS_MOVEMENT
XBLNR_SD
0080014044
3333333333
0080014044
EMKPF
000000000000000000          ######
2222222222333333333333333333222222222200000022222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
ATPDT
000000           0
2222222222333333222222222223
0000000000000000000000000000
PREFETCH34
00000000000000
22222222222222222222222222222222222222222222222222222222233333333333333222222222222
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
FCOD-ST
ST
55222222222222222222
34000000000000000000
%_VIASELSCR
0
4
XMKPF-XBLNR
0080014044
3333333333222222
0080014044000000
XMKPF[]
Table IT_532[1x205]
4A940D940000400010000000C000FFFF0000ED001000C380
83A281F20000610042001000D000FFFF4E20050000001000
XMKPF
80049000331532008WLWLPR20080125200801252008012423504100000000SAPUSER         0080014044
3333333333333333354545533333333333333333333333333333333333333545554522222222233333333332222222
800490003315320087C7C0220080125200801252008012423504100000000310535200000000000800140440000000
XMSSA
000000 000000###############################################
2222222222222222222222222222222223333332233333300000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000C000000C000000C000000C000000C000000C00000
MDVER[]
Table[initial]
0000FFFF
0000FFFF
L_MEM_ID
MKPF-XBLNR
4454254445
DB06D82CE2
RSJOBINFO
00000000000000                                  ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XEKPK_KEY
00000
222222222233333
000000000000000
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMKPF-XABLN
2222222222
0000000000
%_DUMMY$$
2222
0000
XDBEFU
00000 ##############                             #######       0000#############      ######
3333320000000000000022222222222222222222222222222000000022222223333000000000000022222200000022
000000000000C000000C00000000000000000000000000000000000C0000000000000C00C000000C00000000C00C00
GT_SUBCON_PARENT
Table[initial]
0000FFFF
0000FFFF
SY-SUBRC
0
0000
0000
TBSL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
00000000EEDDDDDDDDDDDDEDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD0000DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
MDM07I-BTEXT
FUSS+4215(16)
0000010661000010
3333333333333333
0000010661000010
L_ATPCC
    ########00000000########00000000########00000000###############00000000########
0002222200000000333333330000000033333333000000003333333300000000000000033333333000000002
00C0000000000000000000000000000C000000000000000C00000000000000C0000000C000000000000000C0
FUSS-EXWRT
0000000
000000C
IMSEG-DMBTR
No.       9 Ty.          FORM
Name BELEG_SICHERN_POST
BS_CHECKBOX
2
0000
2000
LIKP
8000080014044SAPUSER     23453420080124      SCCLENSULF   X20080129200801282008012820080129200
3333333333333545554522222333333333333332222225444445544222533333333333333333333333333333333333
800008001404431053520000023453420080124000000333C5E35C6000820080129200801282008012820080129200
BS_PUSHBUTTON
0
0000
0000
V50AGL
00X          B         X      ####                          Ol4kQoiVBas4}R6ApXF7YW
2222223352222222222422222222252222220000222222222222222222222222224636566546737534754355222222
000000008000000000020000000008000000000000000000000000000000000000FC4B1F962134D261086797000000
VBSK
0000000000000000000000#######   #######
2222222222222222222222222233333333333333333333330000000222000000022222222222222222222222222222
000000000000000000000000000000000000000000000000000000C000000000C00000000000000000000000000000
%_DUMMY$$
2222
0000
T683C
2222222222222222222222
0000000000000000000000
WA_ZAEHL
1
0000
1000
CHAR1
1
3
1
SYST-REPID
SAPMV50A
5454533422222222222222222222222222222222
310D650100000000000000000000000000000000
EMKPF-SUBRC
1
0000
1000
CVBEP[]
Table IT_165[0x472]
0000000000006000A0000000D000FFFF0000F0002000C180
0000000000003000500000008100FFFF4000060000001000
ABR_VOR_GABJA
0000
3333
0000
XLIKP[]
Table IT_253[1x1016]
5A74785400008000F0000000F00000000C00D0001000C180
02D280920000B000D0001000830000004910070000001000
XLIKP
8000080014044SAPUSER     23453420080124      SCCLENSULF   X20080129200801282008012820080129200
3333333333333545554522222333333333333332222225444445544222533333333333333333333333333333333333
800008001404431053520000023453420080124000000333C5E35C6000820080129200801282008012820080129200
<%_L170>
VBAP_GESAMTNETZTERMINIERUNG
2
0
<%_L170>-UPDKZ
UPDKZ_DELETE
D
4
4
XLIKP-VBELN
0080014044
3333333333
0080014044
EMKPF
4900033153200800000000000000            ####
3333333333333333333333333333222222222222000022222222222222222222222222222222222222222222222222
4900033153200800000000000000000000000000100000000000000000000000000000000000000000000000000000
DEFAULT_VKGRP
222
000
PACKDATEN_VERBUCHEN
2
0
No.       8 Ty.          FORM
Name BELEG_SICHERN_01
SYST
0000000000000000000000000000000000000000000000000000000000008000000000000000200000000000000000
0000000010000000000000000000000000000000100000001000000010004000000000000000A00000000000000000
IVBPA1KEY
000000
33333322
00000000
IF_FINAL_CHECK
2
0
LF_FLAG_DOCNUM_NEW
2
0
CF_SUBRC
0
0000
0000
KNVP
000                    000000000000000000
2222222222222222222222233322222222222222222222333333333333333333222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
IF_RENUMBER
X
5
8
SPACE
2
0
IVBPA2KEY
000000
22333333
00000000
SY-REPID
SAPMV50A
5454533422222222222222222222222222222222
310D650100000000000000000000000000000000
IF_POST
X
5
8
IVBPA3KEY
000000
22333333
00000000
T180-AKTYP
V
5
6
AKTYP-CREATE
H
4
8
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XSDCTRLFLAG
22
00
No.       7 Ty.          FORM
Name BELEG_SICHERN
IVBPA1_SELIND
000
00C
TVLK-KAPPL
V2
53
62
IVBPA1_LOOPIND1
005
01C
LIKP-WERKS
2222
0000
XVBPAKEY_FEHLER
000000
222222222222233333322
000000000000000000000
IV_FINAL_CHECK_DURCHFUEHREN
2
0
CHARX
X
5
8
LF_SUBRC
0
0000
0000
No.       6 Ty.          FORM
Name FCODE_SICH_OHNE_CHECK
V4231_SHOWN
2
0
%_SPACE
2
0
FCODE
WABU_T
54455522222222222222
7125F400000000000000
FCODE_DEFAULT_UEBERSICHT_1
DEF1
44432222222222222222
45610000000000000000
KOMKD
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
E1EDL32_QUALI
001002
333333
001002
J_1AINFT21
222222222222222222222222222222222222222
000000000000000000000000000000000000000
CFG_SUBITM_DATA
000000
222222222222223333332222222222222222222222
000000000000000000000000000000000000000000
VBAP_ENDE_BEARBEITUNG
2
0
XVBPAKEY
000000
222222222222233333322
000000000000000000000
CVBFA
000000          000000 ########   ########        00000000000000
2222222222222333333222222222233333320000000022200000000222222223333333333333322222222222222222
0000000000000000000000000000000000000000000C0000000000C000000000000000000000000000000000000000
GC_CHK_DO_QUAN_NO_REQ
2
3
2
No.       5 Ty.          FORM
Name FCODE_WABU_VL02
FCODE_ZURUECK1
BAC1
44432222222222222222
21310000000000000000
XVBPA[]
Table IT_31[2x542]
DD641A6400001000100000001000FFFF00002C001000C280
8C92033200002000F0002000E200FFFF40000D0000001400
FCODE_ZURUECK3
BAC3
44432222222222222222
21330000000000000000
XVBUV[]
Table IT_182[0x123]
0000867400006000B00000007000FFFF00009E000000C080
00008CC20000D00060000000B000FFFF4000870090001400
FCODE_ZUSAETZE_FAB
PFZU
54552222222222222222
06A50000000000000000
YVBADR[]
Table IT_32[0x609]
0000C95400001000200000006000FFFF0000DF000000C080
00008B5200003000000000001200FFFF40000C0010001400
FCODE_ZURUECK2
BAC2
44432222222222222222
21320000000000000000
YVBPA[]
Table IT_33[0x542]
0000E95400001000200000001000FFFF00009C001000C280
00008B520000400010000000E200FFFF40000D0000001400
FCODE_VORIGE_POSITION
POS-
54522222222222222222
0F3D0000000000000000
FCODE_REPARATUR
PREP
55452222222222222222
02500000000000000000
FCODE_GEFAHRGUT
KGGP
44452222222222222222
B7700000000000000000
OBJEKTART_IS
IS
45
93
FCODE_GLEICHE_SEITE
ENT1
44532222222222222222
5E410000000000000000
CVBAP
8000000010661000010M1                M1                                                     DI
3333333333333333333432222222222222222432222222222222222222222222222222222222222222222222222244
8000000010661000010D10000000000000000D10000000000000000000000000000000000000000000000000000049
LIPS-VGBEL
0000010661
3333333333
0000010661
No.       4 Ty.          FORM
Name FCODE_BEARBEITEN

Dear Hari
If you have on your own solved the problem, please let me know how you have solved. You have closed the thread without rewarding points to the contributors !!!!!.
Thanks
G. Lakshmipathi

PGI error related to Posting Period issue

Similar Messages

Maybe you are looking for