Hi Matthew,
Select statement would need a where clause to pick records, so have mentioned about version. Not necessary to use that.
Yes it is similar, but instead of using two select statements have asked to move data into Two temporary Result Packages. Then delete unnecessary data, i.e., Keep only relevant data in packages.
My concern here is not to use more select statements.
Hope it is clear!
Thanks,
Umashankar
Hi AK,
Please check the partner detrmination procedure --> Partner Functions settings -> there should be setting for a PF to appear more than once.
Regards
Hi
yes,you can chnnge on PO and on Miro,please explain you want change before GR or after GR.
Best Regards
Ramin
Hi,
If I have understood your requirement correctly, then you can go for two different condition types (OR introduce one additional Condition Type) and have your condition record maintained for the condition types specific to the respective sales area.
That means Condition Type I would appear only for the Sales Area I.
& Condition Type II would appear only for the Sales Area II.
Still if your client insists to go for only one condition type for both the sales areas then you might have to go for Routines to have logic that the "Condition is If the sales area is I then the condition should be mandatory, Else Not mandatory".
Regards
Hi Bala,
Can you please let me know the exact error you are facing ?
Regards
Hi,
Try this code:
MESSAGE s001(T00) DISPLAY LIKE 'E' .
submit <the_name_of_your_program>.
leave program.
Hope it was helpful.
Hi,
The best possible standard solution is to use the standard field available as part of the Customer master --> "Sales Area Data" --> Sales Tab --> Customer Group or any. and bring it as part of your condition record paramter.
Regards
Hi
Does the sample code in the SDK not work?
.../test-resources/sap/ui/commons/FileUploader.html
cheers
dj
Hi Jim,
There is no standard report to accommodate this requirement, we went for a ABAP report in one of our project. data is can be fetched from COSP, COSS.
Br,
Venkat
It is the single selection that is likely to be killing performance, since it contains an OR. Select statements do not have to have any WHERE clause.
For the OP - you should trace via ST05 to check how the SQL optimiser is actually constructing the select from the database.
Hi Darryl,
You may need to restore the db to test environment and try to close this sales order. You may find some other error message that could be helpful.
Thanks,
Gordon
good
I can create the invoice with an earlier date
Hi,
Yes we are planning for
System: SD2 (physical server)
Node1 with A CMS, installed on C drive
Node2 with B CMS (copy of A CMS) installed on D drive
Only one node will be up and running all the time, i mean if node1 is up then node2 will be down
Do you recommended it???
Hi Ryan,
An A/R Invoice can be closed by Incoming Payment, Credit Memo as well as reconciliation.
You may run a simple query to find the JE related to this invoice:
SELECT * from jdt1 T0
WHERE T0.Ref1 like '[%0]%' AND TransType = '13'
Thanks,
Gordon
Do you have further question?
Hi Sarvesh
With latest updated lockbox upload program from SAP, this lines will be posted as on account. In previous version, it used to reject those lines as duplicates, based on check number & customer reference.
Regards
Bhavesh
Hello
I can see two good ways of doing it (there are several possibilities):
1 - As the first reply, create a new program and transaction to build that same front-end as you see into Material Additional Data / Units of measure and then this front-end must call the BAPI_MATERIAL_SAVEDATA passing the values you want, If it's just an unit conversion you can pass by just the values below:
MARM-MATNR (Material number)
MARM-MEINH (Alternative unit of measure) - Bapi field ALT_UNIT
MARM-UMREZ (Numerator) - Bapi field NUMERATOR
MARM-UMREN (Denominator) - Bapi field DENOMINATR
2 - Use a tool like BRO (business rules organizer - www.hks-sa.com) where you can create a rule-based front-end and rule-based processing and releases to the user just the access to the activity "Add unit convertion factors".
Hope it helped.
Bruno
Figured out, creating report on universe, which is not properly migrated to from other environment.
Thanks.
the query does not work, send me the authorization for future authorization
Change tracking is always very tricky. Depending on the specific requirement, usually I also try to evaluate other options:
- is it possible to track changes as they occur? (e.g. a few lines in a user exit writing into a custom table might be easier than a "search expedition" afterwards);
- is it really necessary to track the changes? (e.g. if it's an interface to an external system, it's sometimes easier to just dump all we have in SAP there and let the other system sort it out).
Unfortunately, I'm not that familiar with equipment master to confirm table links, but it's clear that first approach doesn't cover all the bases, so it would have to be combined with the second approach. I didn't quite get why you said it's working till step 5. If you have EQUNR, why can't you get the data?
