Posting date issue for COGI records.

Hi all,
I have one issue regarding the posting date for the records which are being cleared from COGI.
_In case of MF47 (Postprocessing for REM) following is the behaviour,_
In this if GR has happened on say 1st and due to stock un-availability components are gone to Post processing, Now when stock of component inwarded on say 20th then GI posting happens on 20th in post processing record clearance
_Now in case of COGI (Automatic goods movement : Error handling) behaviour is different,_
In this scenario if GR has happened on say 1st and due to stock un-availability components are gone to Post processing (COGI), Now when stock of component inwarded on say 20th then GI posting happens on 1st in post processing record clearance
I want same should be happened in case of COGI also, is there any note/ correction/option available??
Thanks in advance
Regards,
Vinayak.

Dear,
There are backlogs from the backflush in repetitive manufacturing. You can display these using Transaction MF47 and/or Transaction COGI. So schedule a job for program RMSERI11 on daily basis or hourly basis so it will clear the postprocessing errors.
But for some of the errors, it needs manual intervention like updating storage location, posting dates due to posting period block etc.
Hope clear to you.
Regards,
R.Brahmankar

Similar Messages

GR document and posting date issue for initial stock upload are overidden

Hi all
Loading initial stock into the system using standard idoc message type MBGMCR and basic type MBGMCR02.
We are trying to post the intial stock upload with posting and document dates in past with this idoc. The Idoc is accepted with these dates but while posting the system is overiding these dates and posting the document with system date. Any clue as to what is happening?
Regards,
Amit

Hi Jurgen
I am aware about the posting being possible till the last period.
But the system over-riding the posting and document dates in the IDoc even if I chose previos day's date in the current period. The dates in the IDoc are correct to be in the past. The IDoc is accepted by the system with the document and posting dates in the past.
But dates in the document after posting are system dates. Very unsual. Please let me know the reasons.
Thanks for the reply.
Cheers,
Amit

Post goods issue for outbound delivery in previous month

Hi experts,
Pls help. Many thx.
Due to roll out, some stock need to be issued in previous month. It works fine except some deliveries. Those deliveries have been cancelled goods issue due to wrong posting date.
For e.g. the posting date in delivery should be April 1. Due to oversight, the date is entered as May 27. In VL09, the reverse date should be in May. Otherwise, the system disallows further.
Now, the problem comes up. When doing those deliveries again (even create new deliveries), the error message pops up "Deficit of SL Unrestr. prev. 350 KG : XX material XX plant XX storage location
Message no. M7021
Diagnosis
Shortfall below the specified stock level or quantity amounting to 350 KG.
System Response
If the message is an error message (E), the above is not allowed.
If the message is a warning message (W), the system will allow your input, but the warning is intended to prevent you entering a wrong quantity.
Procedure
In the case of a warning message, check the quantity entered.
In the case of an error message, change the quantity or terminate processing."

Hi Lakshmipathy,
I tried the same as you said but its throwing the error below:
GI for delivery 80014996 cannot be canceled for the following reasons:
Cancellation date 30.04.2009 is before the goods issue date 28.05.2009.
I don't have the any issues but i tried whether its working or not.
Kindly suggest...
Regards,
SK

Query regarding the data type for fetcing records from multiple ODS tables

hey guys;
i have a query regarding the data type for fetcing records from multiple ODS tables.
if i have 2 table with a same column name then in the datatype under parent row node i cant add 2 nodes with the same name.
can any one help with some suggestion.

Hi Mudit,
One option would be to go as mentioned by Padamja , prefxing the table name to the column name or another would be to use the AS keyoword in your SQL statement.
AS is used to rename the column name when data is being selected from your DB.
So, the query Select ename as empname from emptable will return the data with column name as empname.
Regards,
Bhavesh

Post Goods Issue for movement type 351

Hi experts,
I need to perform a post goods issue for the movement type 351.
which bapi we need to use? is it going to be "BAPI_GOODSMVT_CREATE" or something else.
What are the information that we require other than movement type for performing post goods isue?
Any pointers on this will be highly appreciated.
Regards,
Sajith

Hi ,
Thanks man.. Then where should I do that.
Idoc is PORDCR102. Message type is PORDCR1.
My requirement is to create a STO first in the user exit EXIT_SAPL2012_001 and then to perform a Post goods issue in the user exit EXIT_SAPL2012_003.
Can u please explain it.
Regards,
Sajith

FM posting date issue in extended classic

We are experiencing issue with SRM deriving incorrect posting period when PO changes are made. We are in extended classic scenario with two FM periods open across fiscal years.
PO changes “No further confirmation” and “No further Invoice” from “No” to “Yes”, changes to anything on Account assignment(Asset, GL account, fund etc).
Earlier when we were in Classic scenario, we had FMOD capability to post the FM documents in previous year and current year. Do we have similar functionality retained in extended classic?

Hello Ratnakar,
could you please check below OSS note:
1981805 - Document Date is always updated with FM Posting Date
You could also check for OSS notes dealing with PSM-GPR-POR application area.
Regards.
Laurent.

Delta enable custom func mod data source for Delete record also

Hi,
We have a custom function module data source and the base table on which data is extracted has two time stamp fields ( created on, changed on ) and the data source is delta enabled with the timestamp field.
It works aboslutely fine in Full and initial mode and load data into a target ODS.
Even in delta mode we believe that it works in most of the cases( only change of an existing records and creation of new records). However in the case of delete, we have issues. When the data is deleted from the base table we completely loose the record and cant advice the BW which one to delete.
In order to bypass this we have analyzed the cdhdr/cdpos table and found out that that we can compute the Key field value that was deleted from the last delta run and can include it as such in the data that are extracted.
Big Question is by what mechanism we let the BW know that this is a delete, so that the existing record( with the same key) is actually deleted from the ODS. I have seen some fields like 0RECORDMODE doing things in SAP delivered content. But not sure how we can get this work for our custom data source.
Please let us know whether you need any clarification on this. I shall be prompt to provide points who can resolved this showstopper issue for us.
Thanks

Hi Aruna,
I have tried to explain : "Big Question is by what mechanism we let the BW know that this is a delete"
Now to create a DataSource, you will have to include the information from the Tables as you mentioned:
1: CDHDR
2: CDPOS
In this table you can check the CHANG_ID as the field which gives the information of
1: Overwrite
2: Add
3: Delete
Now when you create the Function Module, make a field similar to this and read the R/3 Table field CHANGE_IND and pass the relevant Indicators to the BW in the Transfer Rules
Like
CDHDR refers 'D' for delete but In BW 'R' denotes Deleted image. So the FM should take care this and pass the blank for all and 'R' for the documents with 'D' for each line item along with the other required fields.You will have to use an ODS in this case.
note: Plz check the logic of Change Ind "E". I am not sure of this type.if you want to delete 'E' then pass the value as 'R' to the BW system for documents with 'E' CHANGE_IND.
Hopes i made it clear.
regards
Happy Tony
Points == Thanks

Data Load for 20M records from PSA

Hi Team,
We need to reload a huge volume of data (around 20 million records) of Billing data (2LIS_13_VDITM) PSA to the first level DSO and then to the higher level targets.
If we are going to run the entire load with one full request from PSA to DSO for 20M records will it have any performance issue?
Will it be a good approach to split the load based on ‘Billing Document Number’?
In Case, If we the load by 'Billing Document Number'; will it create any performance issue from the reporting perspective (if we receive the data from multiple requests?) Since most of the report would be ran based on Date and not by 'Billing Document Number'.
Thanks
San

Hi,
Better solution put the filter based on the year and fiscal year.
check the how many years of data based on the you can put filter.
Thanks,
Phani.

Posting data issue

Hi,
While creating MIRO my user has given document date is in future but posting date is in past. Whether system will permit to post document ?
Please help me.
Regards
R.Sasikumar

Hello,
Yes, you could post the document you have mentioned.
But if the posting period is difference from the current one, system will issue the following information msgs :F5000 and F5192 when you press enter key.
For example, enter the Document Date :12.11.2009 and posting Date :15.09.2009 in FB01, and
current posting period is 10 for calendar month Oct. 2009. in other words, Document Date :12.11.2009 is in period 11, and posting date is in period 9 and currenct period is 10, so system will issue below information msgs:
F5000 ->Period 10 adjusted in line with posting date 15.09.2009
F5192 ->Check - document date is in the future
if document date and posting date are belong to current period 10, then no msg will be issued( for example: posting date = 05.10.2009, document date =15.10.2009).
Hope the above infor. are useful for you!
Best Regards,

Post Goods Issue for Outbound delivery return

Hi, I'm trying to Post a Goods Issue for a returned outbound delivery but I cannot find a function module to do this, I tried using SD_DELIVERY_UPDATE_PICKING but its creating the material against the outbound delivery with status archived, which means it wasn't created.
I also tried using the MB_CREATE_GOODS_MOVEMENT, but this one is creating the material document but not updating the status and the document flow of the delivery.
Thanks,
Pablo

Hi Lopez,
Post Goods Issue with MB_CREATE_GOODS_MOVEMENT FM in VL02N
Regards,
Sravanthi

Terms of payment/cheque post date issue

Hi guys.
On PO and MIRO terms of payment PD15 is being used. How can I make the cheque date post dated.
Baseline date March 18
Due date April 2
On F-58.
I want the cheque date to be April 2 without opening the next period.
Is it possible at all?
Can someone help me please.
Thanks.

Hi,
I think it is not possible to give future date as posting data unless period is open.
We can do the same by opening two posting periods simultaneously by doing authorization objects in OB52. This object will be tagged to a particular role with specific users and deactivating for all other roles.
Other alternative: We can create a post dated cheque through a manual check by changing the date in the manual check.
Thanks,
Padmaja

I can't post goods issue for the outbound delivery

I select the indicator of GI via delivery in transport block via TCODE OPKP and assign the production profile to the work schedule view of the material master.then I create a production order for the material and release it.I do the wm material staging for the producion order via TCODE LP10,An outbound delivery was created automatically and the movement type is 261.then I pick for the delivery and confirm the transfer order.When I do the post goods issue there is a error message .
E M7 226
Update control of movement type incorrect (entry 261 X X _ _ _ V )
then I see the onlinehelp,I find the configurations are ok.
the content is following in table t345.
werks supply area material staging indicaor
1000   PVB 1310WM     1                         1   wmpp   10000

Please kindly refer to the attached notes below :
523509     FAQ: Control tables (no Customizing)
161729     M7226 with KZVBR=V
Hope this helps.

Making posting date mandatory for FCH8 transaction

Hi Friends,
Can any one of you have idea of how to make the posting date as mandatory in the transaction <b>FCH8</b> either through some configuration or using some exit?
Thanx in advance,
Ram

Hi,
Create a validation for the same through t.code:ob28
regards
Prasad

Content Conversion issue for header record

Hi,
We have a very urgent question on an issue here with one of our XI objects.
This is an inbound interface from an external system into R/3 & BW. The inbound file has a header record (with about 8 fields) and detail records (about 900 fields per detail record). Data going into R/3 & BW don't have header records and everything goes in as detail records. One field from the header of this source file should be passed to the target structure at the detail level. Also, we are NOT using BPM.
Can someone help us how we could define the file content conversion parameters for File adapter.
Thanks in advance ......
Prashant

I'm so sorry, I wasn't subscribed to this thread and I didn't realize there were responses.
If you have a message type made up of a Header with 1 occurence and Detail with 1 to unbounded occurunces, you'd want to do the following in content conversion:
Document Name - your message type
Document Namespac - your message type namespace
Recordset Structure - Header,1,Detail,*
Recordset Structure - Ascending
Then you'll need to set some of the parameters, depending on the layout of your incoming file.
As for the problem of having hundreds of fields, I'm less sure about that.
Would it be possible to break your detail data type down into smaller data types. Each with fewer fields. You'd still have to maintain every field in content conversion, but at least they'd be in seperate parameters, instead of all 900 in one tiny box.
Here's a very rough example of what I mean:
If you have 900 fields, instead of making 1 data type of detail, you could make 9 data types, Detail1, Detail2, Detail3, Detail4, Detail5, Detail6, Detail7,Detail8, Detail 9, each with 100 fields in them (or more with even less fields).
Setting things up the file content conversion would be more complex in this scenario, so it might be a toss up if it's worth it to break it up this way or not if it meant configuring quite a few more parameters.
For example,
You'd have to declare your recordset structure like Header,1,Detail1,,Detail2,,Detail3,* etc, and you'd have to make sure to set the .endSeparator to '0' for all of the first 8 details, so it would recognize that they were all on one line.
I hope this helps a little bit.

Posting Data Issue with IDOC Type : COND_A03

Friends,
I'm posting the data from Middleware(Message Broker) to SAP using the IDOC Type : COND_A03 with Message Type : COND_A.
For this IDOC,I'm populating the below Segment's data.
Segement :E1KOMG:
Fields:
KVEWE,KOTABNR,KAPPL ,KSCHL,VAKEY ,KONDA,MATNR .
Segement :E1KONH:
Fields:
KNUMH,DATAB,DATBI
Segement :E1KONP:
Fields:
KSCHL,STFKZ,KSTBM,KSTBW,KRECH ,KBETR,KONWA,KPEIN,KUMZA,KUMNE,MXWRT,GKWRT,ZAEHK_IND ,KBRUE,VALTG,
VALDT,ANZAUF,MIKBAS,MXKBAS,KOMXWRT,KLF_STG,KLF_KAL
Problem: In SAP, IDOC's are processing successfully with status 53 and updating the tables : KONH,KONP successfully.
But Table A957 which is passing against KOTABNR field is not pupulating with the Materials passing.
Can anyone please guide me why the Materials are not populating in the table : A957.
Regards,
Sreeram

Hi,
I guess there might be some issue with VAKEY population.
All the key fields in A957 should be concated properly while populating VAKEY. (Leading zeros must be prefixed to the material)
Regards,
Ganga

Posting date issue for COGI records.

Similar Messages

Maybe you are looking for