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.

Similar Messages

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

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,

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

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

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

0IC_C03 Inventory Control Data Issue

Dear Gurus,
We have implemented BI 7.0 with the latest support package as of 1st May 2011. Issues are coming relavent to 0IC_C03 infocube for inventory control. I have followed the how to guideline but issues are there.
I have done the following settings:
1:To fill up the extractor for 2LIS_3_BX i have used the Transaction MCNB (All Stock Including non-valuated).
2: To fill up the extractor for 2LIS_3_BF i have used the Transaction OLI1BW (Posting Date till 2999).
3: To fill up the extractor for 2LIS_3_UM i have used the Transaction OLIZBW (Posting Date till 2999).
4: To generate the IP for 2LIS_3_BX for the opening stock balances the update mode CREATE OPENING BALANCE is not showing so i have used the update mode Generate Initial Status.
5: After running the IP for 2LIS_3_BX i run the DTP with extraction Mode "Initialize non commulative".
6: In the infocube Manage for 0IC_C03 i go in the collapse tab and enter the 2LIS_3_BX Request ID and uncheck the "NON Marker Update" to compress the request.
7: I generate the IP & DTP for both 2LIS_3_BF & Then 2LIS_3_UM and compress both the requests in the cube by the checking the "NON MArker Update"
8: When i run the query the data is not coming out right. Some records have negative values and some have wrong values.
Kindly tell me what to do.
Also, ive seen people using 2LIS_3_BF & UM only but not BX. How will this solution be implemented?
Regards,
Shahzad Khero

Dear Guru,
As off now here are the issues:
Quantity Total Stock is matching the stock in ECC 6.0 in transaction MB5B. The issue lies with the Issue Quantity Total Stock
& Receipt Quantity Total Stock. The values are not showing accurately but the new balance per posting date are showing accurately.
For e.g. Cube: 0IC_C03
Calendar Day     Issue Quantity Total Stock           Receipt Quantity Total Stock                          Quantity Total Stock
03/31/2010                           0.000 MT                                 63.000 MT                                                63.000 MT
04/1/2010                           78.940 MT                                 91.410 MT                                                75.470 MT
04/2/2010                           18.000 MT                                 0.000 MT                                                57.470 MT
MB51
Posting Date      Issue Quantity Total Stock           Receipt Quantity Total Stock                          Quantity Total Stock
03/31/2010                           0.000 MT                                 63.000 MT                                                63.000 MT
04/1/2010                           68.940 MT                                 81.410 MT                                                75.470 MT
04/2/2010                           18.000 MT                                 0.000 MT                                                57.470 MT
As you can see the issue & reciept docs are different but the impact on quantity total stock is fine. On top of that the material documents showing in PSA are slightly more than actual showing in MB5B & MB51. Some material documents are showing as a debit entry as well as credit entry in PSA but in reality they have a debit entry or a credit one. Kindly give me a feedback.
Regards,
shahzad

Extended Classic Scenario - SHC: Buffer table not up to date

Hello all,
I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
According to SAP note 944918 the following indicator should not be required to be set:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
What is causing this failure in my SHC?
I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
Thanks & Regards,
Berend Oosterhoff
SRM Consultant Accenture Technology Solutions - The Netherlands.
BAdI BBP_EXTLOCALPO_BADI:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
data definition----------------------------------------------------*
DATA:    wa_mattype     TYPE BAPIMATDOA,
           wa_char18      TYPE MATNR,
           attrib_tab     TYPE TABLE OF bbp_attributes,
           wa_attrib_tab TYPE bbp_attributes,
           wa_value       TYPE om_attrval,
           wa_product_id TYPE comt_product_id.
    bbp_extpo_gl-bbpexpo = 'X'.
from here I did the specific selection for the SC, but that's not relevant here.

Hi Prashant,
Thanks for your quick reply!
Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
Any other thoughts?
Regards,
Berend

Extended Classic PO Replication Issue

We currently use the extended classic scenario for SRM 4.0 and ECC 5.0. After a recent system refresh purchase orders currently no longer replicate to the ECC system in our Q system. I've confirmed that the RFC destinations are set up as well as material groups and HR data replicated fine. Any help and ideas as to why POs are not replicating would be helpful.
PO changes are also not replicating from SRM to ECC.

Hi Chris
is refresh happpened only SRM system or r/3 system or both systems?
hope basis people done post refresh activities like running BDLS and attribute logical system changes.
make ensure that via SCC4 - for your clients (both r/3 and srm) logical system names are pointing to expected logical system not production logical system.
check sm59 connections? any rfc user has locked?
regards
muthu

Restrict goods issue if stock on posting date is zero

Requirement:
Current Inventory period : July 2011
Stock of a material from 01.07.2011 to 30.07.2011 is zero(in MB5B report)
I upload stock of material or GRN occur on 31.07.2011. Say Quantity u2013 100
Now stock as on 31.07.2011 is 100 in MB5B
Still, Stock of a material from 01.07.2011 to 30.07.2011 is zero(in MB5B)
Now, If I do goods issue of a material quantity 100 on 15.07.2011. System allows goods issue. though opening and closing stock as on 15.07.2011 is zero.
After goods issue transaction if I check stock of material on any date between 16.07.2011 to 30.07.2011 , The opening stock and closing stock shows negative.
I want to restrict goods issue if stock on posting date is zero or less then stock available on posting date.
Please suggest

Hi,
This is not the way SAP is designed. As the previous speakers wrote (and as you noticed yourself), SAP maintains stock figures in the database per month rather than per day. MB5B makes complex calculations in order to find out how much stock you had on a specific date - as you probably noticed on the response time. Performing such calculations every time you do a GI would be unfeasibly heavy task for the system - remember there are organisations that perform hundreds of inventory movements a minute!
An alternative solution I suppose would be to maintain the daily stock figures in the database. This would make the finding of the stock figure very quick, but on the other hand, the maintenance of such table would be unfeasible - if you post today a GI on say July 1st, you would need to calculate 36 stock figures and update 36 database records!
Hope this explains the technical issue.
BR
Raf

Good issue to Production order - Allows it in back posting date

Dear all,
Good issue to Production order ( 261 Movement ), allows us to post the component in back dated eventhough stock is not avaible on that date.
Example - Component stock on date 10.02.2010 = Zero , I made it Good receipt on date 18.02.2010 and now stock is available on date 18.02.2010.
Now GI to Production it allows the qty on current and back Posting date also , I want control on date with error message. It should not allowed the GI for back date from 18.02.2010.
Because of this our MB5B report shows the negetive issue qty if i post in back date.
Waiting for reply
Thanks and Regards,
Saurabh

Hi SAurabh,
PLease check whether Negative Stock is allowed for the valuation Area (plant).
GOTO >> SPRO >> MM>> Invetnroy management and physical inventory >> Goods issue/ Transfer Posting >> Allow Negative stock.
Untick the Negative stock allowed for your valuation area (PLant)
Regards,
Pravin

How to fetch post goods issue date and sales order creation date

Hi All,
How to find out the difference between SD Sales Order Item Creation Date and final Post goods issue Date. I would like to know how to fetch those dates and what is the relationship between the tables from which i will get the dates.
Please let me know the solution .
Thanks in advance.

Hi,
Sales order creation date is when u raise a sales order in favor of the customer using VA01.......using ATP logic system purposes the material availability date....
after saving ur sales order...when u raise the Delivery using VL01n w.r.t to OR...than u have to perform picking ....In the picking Tab...specify the amount to be picked than press Post Good Issue....means the goods left the company premises ..
You can the fetch the values using tables- Use T code SE12 or SE16
Vbak-----order header
Vbap-----order item
Vbek-----order schedule line
Likp-----Delivery header
Lips----Delivery item

Goods Receipt and Goods Issue - Posting Date and Document Date Problem

Hi All,
I was using SDK to build own add on to insert Posting Date and Document Date under Inventory> Inventory Transactions> Goods Receipt and Inventory> Inventory Transactions> Goods Issue, but the UI Screen Posting Date and Document Date shown current date.
My SAP Business One version was 2007A SP00 PL42 and alreadly upgrade to SP05.
End up result still the same.
Is there someone can help me?
Thanks you.
Best Regards,
danny

Hi there,
I already solve it by myself.
Actually is i call the initialization twice:
Company.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInventoryGenEntry)
Thats what make this problem happened.
Sorry.
Best Regards,
danny

Special stock partner data problem in ERP system during "Post Goods issue"

Hi all,
I have a (probably) customizing issue in an ERP 6.0 EhP4 test system which not occurs in the ERP 6.0 test system. There is a difference but no one could tell me, what causes the problem in this scenario:
I have two customers, C1 and C2. C2 is the special stock partner (SB) of C1.
I've created a Consignment Fill-up order, then a delivery document based on the order and posted it with "Post Goods Issue". During the update process, a function module (SD_PARTNER_UPDATE) receives partner data in an internal table which contains the sold-to, ship-to and special partner data.
When we tried the same process in the ERP 6.0 EhP4 test system then special-partner data did not occur in the parameter table (I've used the same customers and materials). The special stock partner is probably not taken into consideration due to some customizing settings.
My question is what should I change in the customization to run the process the same way as in the ERP 6.0 system? As far as I know there are no new modifications which have effect on this area, and the used test customers and materials are almost the same - there are no noticable differences.
Thanks in advance.
Akos

I tried setting that field in the sale order this morning. By defaulting it to "C"; I was able to get warning message for TAE line. I was able to post goods with TAE and TAQ, being different quantities. I need the check to determine if TAE and TAQ delivery quantity are different. Using this fields seems to be line specific. Thanks for the suggestion. I now know what that field does to the delivery.
I rewarded points.
Thanks,
Tony

Issue with the Posting Date of the Purchase Order.

Hi All,
There are fields in BW like SSL1: Time OK, SSL2: Qty OK, SSL3: Time & Qty Ok, SSL4: Days Late (Routines are written to calculate). These fields will indicate whether the delivery against a GR is OK or not with respect to Time, Quantity and the No. of Days..
But here the issue I am facing is
If there is only1 delivery/ GR against a single item the calculation in BW are correct - i.e. for a particular PO if there is only one delivery the above fields like SSL1: Time Ok, SSL2: Qty OK will show like the delivery is done within the specified time and everything is OK (in case if it is delivered within the allotted time)
But if there are multiple deliveries or multiple GR's posted for one PO item, the calculations are going wrong i.e. even if the delivery is done well within the specified time it is showing the wrong calculations like it is delievered too late. Because in this case the earlier dates are overwritten.
Can anyone throw me some light on how can I go about solving this issue.
I am thinking of declaring the Posting Date as the KeyField of the DSO as of now it is a Data field I also want to know the impact of assigning this as a Keyfield.
Thanks in advance,
Prasapbi

Hi,
As I understand, you have a DSO based on Purchase Order and your key field is PO and its line item. The problem as you stated will always be there if you have multiple deliveries/GRs created for a single line item because the system will overwrite the entries for same key.
Problem with adding Posting date as keyfield will be that then your key will be PO-PO Lineitem-Date. When PO will be created, the Posting date will be blank(correct me here if I am wrong), therefore you will have one entry for same PO-line item combination. One without date and other with date, which again would be incorrect. If my assumption about Posting date was wrong, even then your data may not be correct because then you may have many entries with same posting date which again would overwrite each other.
If there is any direct link between PO line item and number of deliveries that will get created for them, then you can bring that field in DSO as keyfield. But I don't think there is any such field.
Looking at your report requirement, I would suggest that you make a DSO based on Goods Receipts and then calculate these keyfigures by comparing the dates between GR posting date and PO line item date.
Else you can change the way your datasource works(if its generic one based on function module). Since your main requirement is to check whether the GR posting date has met your SLA or not, you should fetch all the details only when GR is created and make your key field as PO-PO Line item-GR

FM posting date issue in extended classic

Similar Messages

Maybe you are looking for