Hi,
if those WBS are statiscall there will not any settlement even if you pass the WBS in docuemnt level if you don't maintain settlement rule it won't settle it. one more option pass the WBS in a/c doucment text filed or assignment then you can easily find it out .
Regards,
Raman
Hi Ramesh,
Please find below sap notes and link.
1758790 - Error message BL252 - Number 999999 reached. Log is full during Allocation
Message number 999999 reached  log is full | SCN
1964431 - Error message BL252 - Number 999999 reached. Log is full during Archiving
Thanks
Siva
Hi William,
Can you mention the EHP and SP level of your system. Also provide me the SAP note from where
you downloaded the WSDL.
Thanks
Asha
hi,
any business transactions, which you may feel mission critical transactions can be supported, like sales order transaction tcodes.
might be this could help you out IdentifySenarios - End-User Experience Monitoring - SCN Wiki
Check out the video tutorials VideoTutorial - End-User Experience Monitoring - SCN Wiki
Thanks
Jansi
Not my document.
It's supossed to be the thread for Crystal Reports and Visual Studio 2010 installer and redistributable package...
And that's an important detail that I completely forgot to mention, sorry 
Hi Mamta,
For SAP Note 1040369 i found
Each installation package of Livelink® ECM-Suite for SAP® Solutions is protected by a specific password.
This password information together with the installation documentation can be found in the "Installation and Upgrade Guide" of Livelink® ECM-suite for SAP® Solutions.
The installation guide is located on the installation CD in the folder Documentation\manual\english\er-igd.
Please confirm by checking installation CD for Installation and Upgrade Guide.
Thanks,
Gaurav
Hi
We are able to generate form16 when we click on print preview, but it is not generating all the times only few times it is appearing .
Is there any problem with output device.
What will be the issue, Can ay help those who have faced similar issue.
Regards
Sai
Hello Krish, because the BAPI will delete and recreate the SNP order, the (fixed) pegging relationship could not be retained in this case. I'm afraid there's a solution here in standard. You should create the pegging relationship afterwards ...
Hi,
My client has requirement that we need to restrict the street field length to 35 characters in BP transaction.
can any please let me know how can I do it?
Thanks,
Manoj
What is the reason that you need to know about these function modules?
Hai Shiva.
My client having two company codes some time they do STO between two company codes. Material price sholud copy in Billing. so they dont want to create IV billing it should be Profoma. & its DOmastic sales.
Hi Vijaya,
You can also store your string in parts in a table where each part is a size which is allowable by your system.
One of the ways in which I have done something similar to your requirement is save comments in 1002 info type. This info type stores long comments in parts. It basically has the provision of dividing a large string into small parts which linked together.
You can try something similar to this. There are some function modules which can help you achieve this.
Regards,
Karan
Dear M. Abdul Jamil,
Do you mean to add the fields BEGRU and WERKS under the authorisation object for "Material Group (M_MATE_WGR)" or "Material Type (M_MATE_MAR)" ? and How to add these fields under any object ?
Many Thanks,
KH Fong
hi Martin,
First thing, Agentry will not come as a separate installation pack in SMP3.0. Its included as one more component in SMP 3.0 - Agentry toolkit.
Secondly, I guess SMP 3.0 will be released for developer edition and production edition as they did in earlier versions of SMP. But it seems no official documents available so far.
Regards
Yokesvaran Kumarasamy
Hi,
While doing retro for arrears, it will give at a time in one payroll only, no standard for installment payments.
2nd option:
Calculate the Total Arrears amount and divide it by four installments and through IT 0014 with New wage type and give for 4 months as start and end date.
* you have to create a new wage type which is taxable and assigned to IT 0014.
* add this new wt in Remuneration form in Earnings side.
Regards,
Praneeth kumar
Hello Neelesh
For GL account no need to release the edition. You can use the same edition till 9999 and keep adding the records. This is possible for auto replication. If you are using manual replication then you don't have any option but to release the edition.
Regarding cost center / profit center hierarchy or FSV / Cost element, it is necessary to create editions based on the validity date. Edition is imp for hierarchy.
Now once you release the Edition, all the data i.e all your CR's in this edition are available in your next edition. You can surely change any of the records with your current edition. I don't see any issue in this as whenever you release any edition, the data is available for you to change in next edition. Why to go for original data in this case? When you will use the uploaded data? To change any value right? In this case your data is part of old edition but your are using your new edition to make some changes. Now once you do the changes with new edition and release it, the newly changed data is available with your next edition which is logical and serve the governance too.
Kiran
Hi Praneeth,
I used 30 its fixed frm my client. If the pcr is wrong how it works fine in Regular run. I tested it for regular payroll run, it works fine.
Santosh
Hi,
SM13 - Updates are pending
Check whether you have your "update" active or not?
If it is active, double click on update requests and check where these updates are getting terminated (Check for ABAP dumps). There are several reasons to this, Ex: Inactive update process, unavailability of number range, database related issues, program issues etc.
SM12 - Locks last for a long time
Check whether you have long running processes (Dialog/Background)
If you do not have any long running job, then you may delete the lock entries which are not released by system
Regards,
Nick Loy
you can using:
READ itab INDEX RS_SELFIELD-TABINDEX.
then the itab-vbeln will always correct.
regards,
Archer
Dear Suresh,
In ur table , Only mandt is primary key.
That's why system is giving you this type of error.
Please make primary key for combination of mandt and name as per your table's fields.
Regards,
Satyen Trivedi