on 06-02-2011 8:17 AM
Hi All,
I'm trying to close out posting change notices manually by marking the status as U through LU02. Not able to create TO and clear this as the stock is no longer available and these are very old ones.
The problem is that the source and destination data are the same and its throwing an error.
Can you suggest any ways to clear these open posting changes
Regards,
Ashwin
Sap provided corrrection program to clear the posting change notices.Develop this program in your system then check.We are using 4.6c version.
To set the posting change in question to processed (U), please
implement the following correction program in your system.
1) Create program 'ZLTEST00' with type '1' and application 'L' with the
following code:
report zltest00.
tables: lubu.
parameters: w-no like lubu-lgnum, "warehouse number
post-no like lubu-ubnum, "posting change notice
status like lubu-statu, "status
update. "update
select single * from lubu where lgnum = w-no
and ubnum = post-no.
write: / lubu-lgnum,
lubu-ubnum,
'Status old >', lubu-statu,
'Status new >', status.
if update ne space.
update lubu set statu = status
where lgnum = w-no
and ubnum = post-no.
if sy-subrc = 0.
write: / 'Update posting change notice'.
else.
write: / 'No update posting change notice'.
endif.
else.
write: / 'No update posting change notice'.
endif.
To run above correction program:
1) You have to indicate warehouse number, posting change number and the
status which you want to set in the posting change.
2) Without including the UPDATE-parameter, the program only shows the
posting change, or
3) When you mark the parameter UPDATE then the posting change will be
changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is not recommended to update tables via SE16.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.