Hello Julian
CL_MDG_BS_FND_BP_CHECK->EMAIL_ADDRESSES_CHECK.
Please check in this class.
Kiran
Hello Julian
CL_MDG_BS_FND_BP_CHECK->EMAIL_ADDRESSES_CHECK.
Please check in this class.
Kiran
Hi,
regarding "the system is still picking the old partner", I would want to know where/which transaction you checked it?
Regards,
Bowen
Hi Anthony,
As i understand from the screen shot you have created the Quality plan hence in QP02 check with the below inputs i.e.
Plant and material
because if already created quality plan might not valid on what you have given input date
similarly if you are using ECM (Engineering change management) for Quality plan changes then only we will create a ECN (Engineering change note) by assigning the object (which material you are going to change with reference to the ECN) then we will make changes in the quality plan with reference to that ECN Number
so my suggestion to check with plant and material number
then check the validity in QALS table
Regards,
Venkatesh Babu
Hello Fereshteh,
For settlement the currency translation logic is mentioned in note :
201445 - Info: Currency translations in settlement
Best regards,
Jason
Hi,
I think you post the question in wrong space, this space is for topics related to real estate.
Regards,
Bowen
Hi Johan,
Check this:
Is it allowed to Create your own indexes on not... | SCN
Hope it helps.
Thanks & Regards
ANKIT CHAUHAN
SAP Business One Global Support
Hi Michael,
actually the situation that you observe in your system is the intended behavior in a BW 7.40 >= SP6 system.
Please check table RSDCUBELOC field NCUM_REFP_UPD. You should see here value 'Y' for your InfoCube. This means the reference point is updated during compression and all the movements that are part of the compressed request (requid =0) are changed to '2' (historical movements).
This was introduced with BW 7.40 SP6 to allow loading data from a non cumulative InfoProvider into further data targets (SAP note 1949903).
In previous BW 7.40 versions (<=SP5) the value in NCUM_REFP_UPD in table RSDCUBELOC was 'X'. Compression was done by updating the reference points but not changing the recordtp value.
In BW 7.30 the value NCUM_REFP_UPD is space, the compression does not update the reference point.
OLAP execution considers the NCUM_REFP_UPD value and should show the correct stock values for all cases.
Best regards,
Andreas
Hi,
Can you see the queue 0RT_PA_TRAN_CONTROL in RSA7?
If yes then it should update the queue when you execute task to supply data to BW.
Thanks,
Vikrant.
can I expect a response to my query from someone?
thanks.
Hi,
User have opened query in the past? or its new user/machine?
User changed any settings or he updated MS office?
Ask user to take basis team help and reset bex add hoc settings.
Other wise,
Ask user to log into bw server and use Tx - RRMX.
Thanks
try,
onPress: function(event)
{
var fragament = sap.ui.xmlfragment("<fragment name>", this.getView().getController());
fragment.open();
}
And please provide error in your console.
Exactly my point - I would not advise to deactivate generally critical fields check in OVA8 (it can be easily abused and is generally frowned upon by auditors), unless there is a good way to mitigate this risk: e.g. I had a similar requirement - in case selling of certain products we had to force a specific payment term (only one payment term per product code). The business reason was that these products are procured by an affiliated company and are quite expensive. Because of that the company wanted to get the payment for these products earlier than they usually would ask the customer for the regular products. In addition to bypassing critical fields check for the respective combination in OVA8, we implemented an aditional logic in userexit_screen_modification to disallow changing of payment terms for certain sales areas and document types. The payment term determination for the special products was performed by using an automatc not modifiable pricing condition with a specific payment term. In my case not being able to set manually payment terms in certain document types was a decision the country operation made and accepted after receiving an explanation of the process limitations. From audit perspective there were no issues, because the regular users had no way to change manually the critical data fields in the sales documents.
For sure - in case the company uses some additional logic in LVKMPFZ1-3 in OVA8 - it should be checked whether the change could have a negative impact on credit management process.
Regarding the the impact to other sales document types with the same credit group - if two document types need a different treatment from credit management perspective, most probably they should not use the same document credit group - this means additional configuration, you may also need to make some assignments if you already use workflows in the productive environment, but it is easy to monitor and maintain.
The status of BOP executes on daily basis updated with status as U on few days. Most of days its updating as Status X, cant able to find the exact reason behind why its stuck with status on U only on few accasions. Kindly help.
Regards
Pravin
Hi Experts,
I really need your help on this one. The above t-codes by default give single line report. For MC 48, when I click double-line, it generates double line report which has value and stock quantity. Is there a way for the material, short text, current stock value and current stock to be in one or single line?
Thank you so much.
Dear gurus...
Got a question from a colleague regarding moving average price (MAP) for one of her products.
And I can't find the reason for this abnormal MAP.. could someone please comment this one, I've tried to search for a similar situation, but no luck..
Reading documentation for MAP doesn't really help, cause I just fail to see the logic in this particular case:
This is MB51 for the material, last couple months:
Maybe interesting to know, that 23.07.2015 we GR'd 1, total stock = 1.
This is the MBEWH for the last couple months:
This is the valuation from MM:
Looks like theres something weird happening.. no?
Question is, is there a way to see what exactly has happened to the moving price?
All I see is that the Moving price changed the second after goods issue 20.08.2015 for sales order.
And apparently, Amount in LC = MAP at this point.. How can a goods issue have an impact on Moving price....?
Hi,
Check PRD assigned with which G/L accounts for Credit and Debit column in T.code:OBYC.
Also check KDM assigned with account modifier ERA and ERN with which G/L accounts for Credit and Debit column in T.code:OBYC
Regards,
Biju K
Hi Petr,
I didn't fully understand from your question, does this fail in runtime? Because sometimes ESLint gives errors that aren't necessarily mean they will fail at runtime
Yes it can consume data from anywhere apart from sap gateway.
This is a free oData service provided by oData.org http://services.odata.org/V4/OData/(S(hskno54tcbbn0kn5zbgaqggh))/OData.svc/
I didn't understand your second query.
Perhaps you are saying first line in different way.
If you want to use IS_INITIAL function.
You should compare with Row attributes. i.e., data source should be Row Attributes for Actual (KF1)
Also find the attached screenshot with IS_INITIAL(KF1) <> 1.
This covers 2 ways of writing Macro for your requirement. Do let me know if you still need any help.
Kindly close the discussion if resolved. How to close a discussion and why
Regards,
Hussain