Best practice - ap invoice adjustments

Hi
Can anyone let me know whats the best practice to do ap invoice adjustments?
We have couple of invoices with amounts mismatches to emcumbered funds. we need to adjust the invoice amounts to be able to validate and account the invoices.
which is a better option (invoice is not yet validated and accounted):
1. void the invoice and create a new one?
2. reverse lines and make adjustments in the new lines?
Appreciate if someone let me know which is a better option and why?
Thanks
Ravi

Ranjan,
As a SAP customer we use invoice entry in ERP using MIRO and FB60 as these are the most efficient for our busines.
1. Invoice entry using MIRO tcode is faster as it can be done with minimal use of the mouse. Invoice entry is slower in SRM as browser response and interactions with the backed ERP system slows the systems reponse to the user input. Repeated use of a mouse in the SRM browser is detrimental to fast input.
2. Not all types of invoices can be handled in SRM e.g. Invoice without PO.
3. We process approx 20,000 invoices per month with multiple input operators, SRM could not handle that sort of load.
4. SRM is really a procurement application and although invoice entry is included it is probably more for users who wish to use SRM in a stand alone scenario. We use extended classic so all our financial transactions take place in the ERP backend.
Your choice also depends upon the number and quality of the invoices you plan to process, and the need for the operators to be trained on one or two systems.
Hope these personal observations assist with your decision
Regards
Allen

Similar Messages

Best practice for invoice posting inSRM

Dear expert,
what is the best practice for posting an invoice? Is it in SRM system or MM system? In SRM, the system allows one to use approval procedure for invoice posting; wheras in MM, one cannot use the apporval procedure to post an invoice. similar is the case, in SRM-SUS and MM-SUS scenario?
I would appreciate if you can feedback on the industry practice.
thanks and regards,
Ranjan

Ranjan,
As a SAP customer we use invoice entry in ERP using MIRO and FB60 as these are the most efficient for our busines.
1. Invoice entry using MIRO tcode is faster as it can be done with minimal use of the mouse. Invoice entry is slower in SRM as browser response and interactions with the backed ERP system slows the systems reponse to the user input. Repeated use of a mouse in the SRM browser is detrimental to fast input.
2. Not all types of invoices can be handled in SRM e.g. Invoice without PO.
3. We process approx 20,000 invoices per month with multiple input operators, SRM could not handle that sort of load.
4. SRM is really a procurement application and although invoice entry is included it is probably more for users who wish to use SRM in a stand alone scenario. We use extended classic so all our financial transactions take place in the ERP backend.
Your choice also depends upon the number and quality of the invoices you plan to process, and the need for the operators to be trained on one or two systems.
Hope these personal observations assist with your decision
Regards
Allen

Best practices when carry forward for audit adjustments

Dear experts,
I would like to know if someone can share his best practices when performing carry forward for audit adjustments.
We are actually doing legal consolidation for one customer and we are facing one issue.
The accounting team needs to pass audit adjustments around April-May for last year.
So from January to April / May, the opening balance must be based on December closing of prior year.
Then from May / June to December, the opening balance must be based on Audit closing of prior year.
We originally planned to create two members for December period, XXXX.DEC and XXXX.AUD
Once the accountants would know their audit closing balance, they would have to input it on the XXXX.AUD period and a business rule could compute the difference between the closing of AUD and DEC periods and store the result on an opening flow.
The opening flow hierarchy would be as follow:
F_OPETOT (Opening balance Total)
F_OPE (Opening balance from December)
F_OPEAUD (Opening balance from the difference between closing balance of Audit and December periods)
Now, assume that we are in October, but for any reason, the accountant run a carry forward for February, he is going to impact the opening balance because at this time (October), we have the audit adjustments.
How to avoid such a thing? What are the best practices in this case?
I guess it is something that you may have encounter if you did a consolidation project.
Any help will be greatly appreciated.
Thanks
Antoine Epinette

Cookman and I have been arguing about this since the paleozoic era. Here's my logic for capturing everything.
Less wear and tear on the tape and the deck.
You've got everything on the system. Can't tell you how many times a client has said "I know that there was a better take." The only way to disabuse them of this notion is to look at every take. if it's not on the system, you've got to spend more time finding the tape, and adding "wear and tear on the tape and the deck." And then there's the moment where you need to replace the audio for one word from another take. You can quickly check all the other takes (particularly if you've done a thorough job logging the material - see below)_.
Once it's on the system, you still need to log and learn the material. You can scan thru material much faster once it's captured. Jumping around the material is much easier.
There's no question that logging the material before you capture makes you learn the material in a more thorough way, but with enough selfdiscipline, you can learn the material as thoroughly once it's been captured.

Best Practices Invoice communication to 3rd party

Hi All,
I am looking for some pointer on best practices for 3rd party invoice communication for FMCG.
Background: Inhouse printing, wrapping in envelope and posting to customer is an expensive option to client, compared to sending invocie data to 3rd party and 3rd party doing above activities of printing, enveloping and posting to customer.
Currently a text file is sent to 3rd party which is enriched with logo etc and merged into a template to prepare final invoice document. This is then printed by 3P and sent to customer.
Possible Solution: We can continue similar apporach where ECC sends IDOC to PI and PI converts data in text format to 3rd party for enrichment and printing. However this requires development both in ECC and PI and testing at ECC, PI and 3P. Is the suggested approach the best industry practice?
Would appreciate if you can share your thoughts around the topic on best practice adopted in FMCG for third party communication?
Thanks and Regards,
Namish

Best possible solution for your requirement is that you must maintain customer master data with their Email adresses in customer general data tab. Take help from your ABAPER and BASIS guy to activate email sending. Maintain output type for email same like you are using for printing. You must have a smart form for your invoice with company logo and all other information. When you will create invoice a soft copy of that invoice in PDF format will be sent automatically to that particular customer.
For this you need to do some configuration for out put type. ABAPER will help you to convert invoice into PDF and BASIS guy will activate email sending. You can also search the forum for more help. Email output type in PDF format have been many time discussed.
Hope it will help you in your requirement.

Manage vendor bank account in company code level - Best practice

hi,
we have on our client several company codes, and we are thinking how to manage the vendor bank accounts in company codes level or in centeral level.
our problem with company codes level is that the vendor bank accounts define in a centeral level so technically with sap standard it is not possible. if anyone can tell me that this is possible i will be very happy to know.
in centeral level our problem is with the business process because of we do not have a person (functionalism ) that can be responsible for all the company codes, basically every company shoule be responsible for her vendors
please advice what is the best practice to manage vendor bank accounts in enviroment of several company code
regards,
meir

hi Raghu,
i know that but this is not my qusition.
which company code will be responsible to enter the bank account in the vendor master data? as i say the vendor bank accounts manage in centeral level and not in company code level and this is our problem and i like to know how other companies with the same situation handle with this issue
and also after we have the bank accounts in the vendor master data what happend if for one vendor has several bank accounts one for every company code? how the payment program F110 could know automaticaly which bank account to take (i know that there is an optoin to use Partner bank type in the vendor master data, and enter this PBT when posting the invoice of the vednor, but this is not good because of we do not want the the accountant will be responsible from which bank the vendor get his money).
regards,
meir

Best Practice - What a complete PO means?

Hi! I would like to determine the best practice to managing the PO process and ensuring that the PO is in a state ready for archiving in the future (with minimum efforts to correct the PO).
Is it fair to say that a PO is considered 'complete' if the Complete Delivery indicator and invoiced quantity equals that of the final goods receipted quantity? Or do we have to be more stringent in the definition in that the goods receipted and invoice quantity has to match that of the ordered quantity?
For example:
PO Qty = 5
GR Qty = 4 (complete delivery indicator turned on)
IR Qty = 4
In the above example, is the PO considered complete? The reason why I ask is because I understand the PO can only be archived if it is set with Deletion Flag, and when I manually try to delete the PO, an error is output indicating that the quantity delivered is smaller than the quantity ordered (assuming no under delivery tolerance is maintained here). So, in this case, is it good practice to always update the PO quantity to match that of the final receipted quantity?
Appreciate your advice on the above.
Cheers!
SF

Hi,
If PO qty is 5 & GR qty is 4..
you can flag the PO as Delivery completed..
Logically the PO will be considered as Closed for procurement..
It is Some times not possible to change the PO qty to GR qty..bcz basing on the Settings.. it may trigger again release strategy also..
Basing on your business requirement either u can go for changing the PO qty to GR qty
or marking the Delivery completed..
Thx
Raju

Font sizing best practice in 2014

Decided to obtain a better working knowledge of font sizing best practice, read until my eyes bled, and find I continue to have questions. So much posted is old (older than few years) and change happens fast.
To the point; Since use of em units (or percentages) is often preferred, I now see that rems (root em) is another option, which leads me to ask:
Should I consider using “rem” sizing?… or, do browser zooming capabilities of modern browsers mean I do not have to obsess over how precise I must be in guesstimating how viewers actually see my written content as they have better control at their end? Is em compounding of sizes something that must be considered?
Thanks-

Use a mixture of what is best suited.
For document level I use pixels as in
/* Document level adjustments */
html {
font-size: 13px;
@media (min-width: 760px) {
html { font-size: 15px; }
@media (min-width: 900px) {
html { font-size: 17px; }
Then for the modules I use root level ems as in
/* Modules will scale with document */
header {
font-size: 1.5rem;
footer {
font-size: 0.75rem;
aside {
font-size: 0.85rem;
Then the size that will scale with the modules
/* Type will scale with modules */
h1 {
font-size: 3em;
h2 {
font-size: 2.5em;
h3 {
font-size: 2em;
Using this method I keep each scenario under complete control.
A List Apart has a nice article on the subject.

Best Practice(s) for Laptop in Field, Server at Home? (Lightroom 3.3)

Hi all!
I just downloaded the 30-day evaluation of Lightroom, now trying to get up to speed. My first task is to get a handle on where the files (photos, catalogs, etc.) should go, and how to manage archiving and backups.
I found a three-year-old thread titled "Best Practice for Laptop in Field, Server at Home" and that describes my situation, but since that thread is three years old, I thought I should ask again for Lightroom 3.3.
I tend to travel with my laptop, and I'd like to be able to import and adjust photos on the road. But when I get back home, I'd like to be able to move selected photos (or potentially all of them, including whatever adjustments I've made) over to the server on my home network.
I gather I can't keep a catalog on the server, so I gather I'll need two Lightroom catalogs on the laptop: one for pictures that I import to the laptop, and another for pictures on the home server -- is that right so far?
If so, what's the best procedure for moving some/all photos from the "on the laptop catalog" to the "on the server catalog" -- obviously, such that I maintain adjustments?
Thanks kindly! -Scott

Hi TurnstyleNYC,
Yes, I think we have the same set-up.
I only need 1 LR-catalog, and that is on the laptop.
It points to the images wherever they are stored: initially on the laptop, later on I move some of them (once I am am fairly done with developing) within LR per drag&drop onto the network storage. Then the catalog on the laptop always knows they are there.
I can still continue to work on the images on the network storage (slightly slower than on laptop's hard drive) if I still wish to.
While travelling, I can also work on metadata / keywording, although without access to my home network the images themselves are offline for develop work.
2 separate catalogs would be very inconvenient, as I would always have to remember if I have some images already moved. No collections would be possible of images including some on the laptop, some on the network.
Remember: a LR catalog is just a database with entries about images and the pointer to their storage location.
You can open only 1 DB of this sort at a time.
There is no technical reason for limiting a LR-catalog - I have read of people with several hundert thousand images within one.
The only really ever growing part on my laptop with this setup is the previews folder "<catalog name> Previews.lrdata". I render standard previews so that I can do most of the work for offline-images while travelling.
The catalog itsself "<catalog name>.lrcat" grows much slower. It is now 630 MB for 60'000+ images, whereas previews folder is 64 GB.
So yes, I dedicate quite a junk of my laptop hard disk to that. I could define "standard"-previews somewhat smaller, fitting to the laptop's screen resolution, but then when working at home with a bigger external monitor LR would load all the time for the delta size, which is why I have defined standard-preview-size for my external monitor. It may turn out to be the weakness of my setup long-term.
That is all what is needed in terms of Lightroom setup.
What you need additionally to cover potential failure of drives is no matter of LR, but *usual common backup sense* along the question "what can be recreated after failure, if so by what effort?" Therefore I do not backup the previews, but very thoroughly the images themselves as well as the catalog/catalog backups, and for convenience my LR presets.
Message was edited by: Cornelia-I: sorry, initially I had written "1:1-previews", but "standard previews" is correct.

Best practice for PK and indexes?

Dear All,
What is the best practice for making Primary Key and indexes? Should we keep them in the same tablespace as table or should we create a seperate tableapce for all indexes and Primary Key? Please note I am talking about a table that has 21milion rows at the moment and increasing 10k to 20k rows daily. This table is also heavily involved in daily reports and causing slow performance. Currently the complete table with all associated objects such as indexes and PK is stored in one seperate tablespace. If my way is right then please advise me how can I improve the performance of retrival or DML operation on this table?
Thanks in advance..
Zia Shareef

Well, thanks for valueable advices... I am using Oracle 8i and let me tell you exact problem...
My billing database has two major tables having almost 21 millions rows each... one has collection data and other one for invoices... many reports are showing the data with the joining of Customer + Collection + Invoices tables.
There are 5 common fields in between invoices(reading) and collection tables
YEAR, MONTH, AREA_CODE, CONS_CODE, BILL_TYPE(adtl)
My one of batch process has following update and it is VERY VERY SLOW:
UPDATE reading r
SET bamount (SELECT sum(camount)
FROM collection cl
WHERE r.ryear = cl.byear
AND r.rmonth = cl.bmonth
AND r.area_code = cl.area_code
AND r.cons_code = cl.cons_code
AND r.adtl = cl.adtl)
WHERE area_code = 1
tentatively area_code(1) is having 20,000 consumers
each consuemr may have 72 invoices and against these invoices it may have 200 rows in collection tables (system have provision to record partial payment against one invoice)
NOTE: Please note presently my process is based on cursors so the above query runs for one consumer at one time but just for giving an idea I have made it for whole area.
Mr. Yingkuan, can you please tell me how can I check that the table' statistics is not current and how can I make it current. Is it really effect performance?

SAP best practice on scheduling agreements

Hello all,
Our client is an automotive supplier and currently in the SAP environment we use spot POs for indirect purchasing (thru SRM) and scheduling agreement for direct procurement. The scheduling agreements have multiple lines and we try to process as much invoices as ERS as possible.
Currently some of the business units are proposing to have single line items in the SA rather than the multiple ones. The reason being huge no of SA lines being faxed and also supposing it to be a SAP suggested best practice to have ONLY one line item per SA.
I am not sure of any such best practice. Could you please help me with an single Vs multi line scheduling agreements pros and cons. Also what is the best practice that are seen in the automotive sector or being suggested by SAP.
Any SAP official documentation in the public domain will also help.
Thanks

As per my experience, we have used both the ways, both have its pro's and cons.
In one instance we may feel that it is easy to handle one line per one SA and in that way we will create many SA's and in ither instance we may fell having one SA for multiple lines.
SAP does not give any best approach...or else SAP woul dhave provided the option for only one line.
As per my experience the Structuring of a SA should be based on the way you procure from the supplier / Vendor.
We have one supplier who supplies 800+ materials, we can create one SA with 800 lines... But we have created multiple SA's based on the product category whcih is a bit easy to identify whcoih material goes into which SA and the Vendor is also happy as he knows that for one product there is a specific SA.
Hope this helps you in resolving your issue.,

Best Practice in Accounts Payable Processing

Guys,
Would just like to know best practice (or your practice) in Accounts Payable Invoice Processing if its 100% MIRO (3 way match PR-PO-GR) or part MIRO and part Direct Bill?
Our situation is that, the owner of our PR/PO process is the Procurement Department and all of the transaction goes to them are process through MIRO. However there are some puchases and contracts that they are not involve and they dont allow us to use PR and PO (MIRO) process since they are not involved in the negotiation. This transaction we end up paying through direct bill process (manual).
Appreciate assistance.
Thank you!

Hi,
For manual payments we implemented the approval process using workflows.
Hope this helps!
Regards.

Best practice - applying Filters

What's the best practice in terms of performance versus code reuse, when applying filters?
Right now, I see 3 ways to specify a filter:
1. as a <mx:filter> or <s:filter>
2. in actionscript:
var glowFilter:GlowFilter = new GlowFilter();
--OR--
3. in SVG:
<s:rect>
<s:filters>
<s:DropShadowFilter blurX="20" blurY="20" alpha="0.32" distance="11" angle="90" knockout="true" />
</s:filters>
</s:rect>
What's the best way to apply this, in terms of performance? Thanks.

Fredrik,
Though similar to your workflow, here is how I would do it.
Import those "raw" Clips into a Project, and do my Trimming in that Project, relying on the Source Monitor to establish the In & Out Points for each, and also using different Instances of any longer "master Clip.". I would also do my CC (Color Correction), and all density (Levels, etc.) Effects here. Do not Trim too closely, as you will want to make sure that you have adequate Handles to work with later on.
Use the WAB (Work Area Bar) to Export the material that I needed in "chunks," using either Lagarith Lossless CODEC, or UT Lossless CODEC *
Import my music into a new Project and listen over and over, making notes on what visuals (those Exported/Shared Clips from above) I have at my disposal. At this point, I would also be making notes as to some of the Effects that I felt went with the music, based on my knowledge of the available visuals.
Import my Exported/Shared, color graded Clips.
Assemble those Clips, and Trim even more.
Watch and listen carefully, going back to my notes.
Apply any additional Effects now.
Watch and listen carefully.
Tighten any edits, adjust any applied Effects, and perhaps add (or remove existing) more Effects.
Watch and listen carefully.
Output an "approval" AV for the band/client.
Tweak, as is necessary.
Output "final approval" AV.
Tweak, as is necessary.
Export/Share, to desired delivery formats.
Invoice the client.
Cash check.
Declare "wine-thirty."
This is very similar to your proposed workflow.
Good luck,
Hunt
* I have used Lagarith Lossless CODEC with my PrE 4.0, but have not tried UT. Both work fine in PrPro, so I assume that UT Lossless will work in PrE too. These CODEC's are fairly quick in processing/Exporting, and offer the benefit of smaller files, than Uncompressed AVI. They are visually lossless. The resultant files will NOT be tiny, so one would still need a good amount of HDD space. Neither CODEC introduces any artifacts, or color degredation.

BI Best Practice for Chemical Industry

Hello,
I would like to know if anyone is aware of SAP BI Best Practice for Chemicals.And if so can anyone please post a link aswell.
Thanks

Hi Naser,
Below information will helps you in detail explanation regarding Chemical industry....
SAP Best Practices packages support best business practices that quickly turn your SAP ERP application into a valuable tool used by the entire business. You can evaluate and implement specific business processes quickly u2013 without extensive Customization of your SAP software. As a result, you realize the benefits with less Effort and at a lower cost than ever before. This helps you improve operational efficiency while providing the flexibility you need to be successful in highly demanding markets. SAP Best Practices packages can benefit companies of all sizes, including global enterprises creating a corporate template for their subsidiaries.
Extending beyond the boundaries of conventional corporate divisions and functions, the SAP Best Practices for Chemicals package is based on SAP ERP; the SAP Environment, Health & Safety (SAP EH&S) application; and the SAP Recipe Management application. The business processes supported by SAP Best Practices for Chemicals encompass a wide range of activities typically found in a chemical industry
Practice:
u2022 Sales and marketing
u2013 Sales order processing
u2013 Presales and contracts
u2013 Sales and distribution (including returns, returnables, and rebates, with quality management)
u2013 Inter- and intracompany processes
u2013 Cross-company sales
u2013 Third-party processing
u2013 Samples processing
u2013 Foreign trade
u2013 Active-ingredient processing
u2013 Totes handling
u2013 Tank-trailer processing
u2013 Vendor-managed inventory
u2013 Consignment processing
u2013 Outbound logistics
u2022 Supply chain planning and execution Supply and demand planning
u2022 Manufacturing planning and execution
u2013 Manufacturing execution (including quality management)
u2013 Subcontracting
u2013 Blending
u2013 Repackaging
u2013 Relabeling
u2013 Samples processing
u2022 Quality management and compliance
u2013 EH&S dangerous goods management
u2013 EH&S product safety
u2013 EH&S business compliance services
u2013 EH&S industrial hygiene and safety
u2013 EH&S waste management
u2022 Research and development Transformation of general recipes
u2022 Supplier collaboration
u2013 Procurement of materials and services (Including quality management)
u2013 Storage tank management
u2013 E-commerce (Chemical Industry Data Exchange)
u2022 Enterprise management and support
u2013 Plant maintenance
u2013 Investment management
u2013 Integration of the SAP NetWeaver Portal component
u2022 Profitability analysis
More Details
This section details the most common business scenarios u2013 those that benefit most from the application of best practices.
Sales and Marketing
SAP Best Practices for Chemicals supports the following sales and marketingu2013related business processes:
Sales order processing u2013 In this scenario, SAP Best Practices for Chemicals supports order entry, delivery, and billing. Chemical industry functions include the following:
u2022 Triggering an available-to-promise (ATP) inventory check on bulk orders after sales order entry and automatically creating a filling order (Note: an ATP check is triggered for packaged material.)
u2022 Selecting batches according to customer requirements:
u2022 Processing internal sales activities that involve different organizational units
Third-party and additional internal processing u2013 In this area, the SAP Best Practices for Chemicals package provides an additional batch production step that can be applied to products previously produced by either continuous or batch processing. The following example is based on further internal processing of plastic granules:
u2022 Purchase order creation, staging, execution, and completion
u2022 In-process and post process control
u2022 Batch assignment from bulk to finished materials
u2022 Repackaging of bulk material
SAP Best Practices for Chemicals features several tools that help you take advantage of chemical industry best practices. For example, it provides a fully documented and reusable prototype that you can turn into a productive solution quickly. It also provides a variety of tools, descriptions of business scenarios, and proven configuration of SAP software based on more than 35 years of working with the
Chemical industry.
SAP Functions in Detail u2013 SAP Best Practices for Chemicals
The package can also be used to support external toll processing such as that required for additional treatment or repackaging.
Tank-trailer processing u2013 In this scenario, SAP Best Practices for Chemicals helps handle the selling of bulk material, liquid or granular. It covers the process that automatically adjusts the differences between the original order quantities and the actual quantities filled in the truck. To determine the quantity actually filled, the tank trailer is weighed before and after loading. The delta weight u2013 or quantity filled u2013 is transmitted to the SAP software via an order confirmation. When the delivery for the sales order is created, the software automatically adjusts the order quantity with the confirmed filling quantity.The customer is invoiced for the precise quantity filled and delivered.
Supply Chain Planning and Execution
SAP Best Practices for Chemicals supports supply chain planning as well as supply chain execution processes:
Supply and demand planning u2013 Via the SAP Best Practices for Chemicals package, SAP enables complete support for commercial and supply-chain processes in the chemical industry, including support for integrated sales and operations planning, planning strategies for bulk material, and a variety of filling processes with corresponding packaging units. The package maps the entire supply chain u2013 from sales planning to material requirements planning to transportation procurement.
Supplier Collaboration
In the procurement arena, best practices are most important in the following
Scenario:
Procurement of materials and services:
In this scenario, SAP Best Practices for Chemicals describes a range of purchasing processes, including the following:
u2022 Selection of delivery schedules by vendor
u2022 Interplant stock transfer orders
u2022 Quality inspections for raw materials, including sampling requests triggered
by goods receipt
Manufacturing Scenarios
SAP Best Practices for Chemicals supports the following sales and
Manufacturingu2013related business processes:
Continuous production u2013 In a continuous production scenario, SAP Best Practices for Chemicals typifies the practice used by basic or commodity chemical producers. For example, in the continuous production of plastic granules, production order processing is based on run-schedule headers. This best-practice package also describes batch and quality management in continuous production. Other processes it supports include handling of byproducts,co-products, and the blending process.
Batch production u2013 For batch production,
SAP Best Practices for Chemicals typifies the best practice used by specialty
chemical producers. The following example demonstrates batch production
of paint, which includes the following business processes:
u2022 Process order creation, execution, and completion
u2022 In-process and post process control
u2022 Paperless manufacturing using XMLbased Process integration sheets
u2022 Alerts and events
u2022 Batch derivation from bulk to finished materials
Enterprise Management and Support
SAP Best Practices for Chemicals also supports a range of scenarios in this
area:
Plant maintenance u2013 SAP Best Practices for Chemicals allows for management
of your technical systems. Once the assets are set up in the system, it focuses on preventive and emergency maintenance. Tools and information support the setup of a production plant with assets and buildings.Revenue and cost controlling u2013 The package supports the functions that help you meet product-costing requirements in the industry. It describes how cost centers can be defined, attached
to activity types, and then linked to logistics. It also supports costing and settlement of production orders for batch and continuous production. And it includes information and tools that help you analyze sales and actual costs in a margin contribution report.
The SAP Best Practices for Chemicals package supports numerous integrated
business processes typical of the chemical industry, including the following:
u2022 Quality management u2013 Supports integration of quality management concepts across the entire supplychain (procurement, production, and sales), including batch recall and complaint handling
u2022 Batch management u2013 Helps generate batches based on deliveries from vendors or because of company production or filling, with information and tools for total management of batch production and associated processes including batch derivation, batch information cockpit, and a batchwhere- used list
u2022 Warehouse management u2013 Enables you to identify locations where materials
or batch lots are stored, recording details such as bin location and other storage information on dangerous goods to help capture all information needed to show compliance with legal requirements
Regards
Sudheer

What is the best practice for genereating seq in parent

I'm wondering what the best practice is for generating seq in parent.
I have the following tables:
invoice(id, date, ...)
invoice_line(invoice_id, seq, quantity, price ...)
There are shown in 1 uix displaying invoice in form layout and invoice lines in tabular layout.
Now I like the seq automaticaly generated by ADF Business Components, not enterable by the user.
The 1st record within each invoice should get seq 1.
Regards,
Marcel Overdijk

Marcel,
I think best practices is to create a database trigger on the tables that obtains the sequence number from a database sequence on insert.
In JDeveloper assign DBSequence as a type to the attribute representing the sequence field in the EO. ADF BC then assigns a temporary value to it. The real sequence number then gets added on submit.
If you want to have IDs that don't miss a single number, then database seuqences may not be a good option. In this case you would use the table trigger to implement your own sequencing.
Frank

Best practice recommendations for Payables month end inbound jobs

During Payables month end we hold off inbound invoice files and release them once the new period is open so that invoice get created in new fiscal period. Is this an efficient way to do? Please advise best practice for this business process.
Thanks

Hi,
Can someone provide your valuable suggestions.
Thanks
Rohini.

Best practice - ap invoice adjustments

Similar Messages

Maybe you are looking for