Road Map for B1 Fresher for more details

Accounting and Financials:
General ledger and journal entries
Basic cost accounting and monitoring of project costs
Budget management
Banking and bank statement processing
Payment processing and reconciliation
Financial statements and reporting
Sales tax and value-added tax
Multicurrency support

Sales and Customer:
Opportunities and pipeline management
Customer contact and activity management
Sales quotations and orders
Invoicing and crediting
Sales and pipeline forecast
Service contract management
Service-call management entry and tracking

Purchasing and Operations:
Purchase proposals
Purchase orders and deliveries
Goods receipts and returns
Accounts payable invoice and credit notes
Bill of materials
Production orders
Forecasting and material requirements planning

Inventory and Distribution :
Items management and item queries
Receipt to stock, release from stock ,and stock transactions
Stock transfer between multiple warehouses
Serial number management
Inventory revaluation
Customer and vendor catalog
Price lists and special pricing
Batch management
Pick and pack

How To Configure The G/L Account Determination – General Tab In SAP Business One

Use this tab to specify general information for G/L account determination.

To access this tab, choose: Administration > Setup > Financials > G/L Account Determination > General.

G/L Account Determination: General Tab

Advanced Rules
Indicates if and to how many advanced G/L account determination rules a given account is assigned. Click the link arrow to view the respective rules in the Advanced G/L Account Determination Rules window.

Credit Card Deposit Fee
Define an account for posting the fee for deposit of credit card vouchers.

Rounding Account
Select a default account to use in journal entries created for rounding differences. This may occur when you define rounding for certain currencies.

Reconciliation Difference
Determines the account to use for the Automatic Balancing Transaction in Automatic Reconciliation.

Period-End Closing Account
Define an account to use when performing a period-end closing process.

Realized Exchange Diff. Gain
When reconciling transactions of foreign currency G/L accounts, an exchange rate differences transaction is performed automatically. Define here the account to which the gained exchange rate difference is posted.

Realized Exchange Diff. Loss
When reconciling transactions of foreign currency G/L accounts, an exchange rate differences transaction is performed automatically. Define here the account to which the lost exchange rate difference is posted.

Realized Conversion Diff. Gain, Realized Conversion Diff. Loss
When you reconcile transactions of G/L accounts that have a balance due in the system currency, conversion differences transactions are performed automatically. Define here the account to which the gained/lost conversion differences are posted.
Note: The fields are available only if the system currency is different from the local currency.

Bank Charges Account
Specify a default account for bank charges posting.
Note: Only expense accounts can be used as bank charges accounts.
Note: The field is not available for Israel.

Instuctions on how to assign a form query to a field:

1.      Open a form.

2.      Click on the field.

3.      Select for the drop down menus at the top of the screen:
Tools->Search Function->Define 

4.      A window will appear. Click on Search by Saved Query. Double Click on the long gray box below that option. The Query Manager will open. Select the query you wish to run on the field you selected.

If you would like to have the value automatically populate when something else happens on the form, check the Auto Refresh When Field Changes box. From the drop down box below that option, select the field that will "trigger" the query to run on the field you selected.

5.      To run the query on demand on the form, press Alt+F2. To change the field’s query assignment later you can press Alt+Shift+F2 and the window above will be displayed. You can also follow the original drop down menu path listed above to perform the same action.

https://goo.gl/WbShwQ

SAP TB Training TB 1000 & TB 1100

SAP TB Training TB 1000 & TB 1100

TB Training 1000 Logistic:
There are five unit
Unit 1 Overview:
In this unit is introduction of SAP B1, Master data and Document.
Unit 2 Purchasing – A/P (Account Payable): In this unit we covered
Procurement Process
• Purchase Order Good Receipt PO A/P Invoice Outgoing Payment

Purchasing Items
Purchase Requisitions and Purchase Quotations
Issues with Goods Receipt POs
Goods Returns
A/P Credit Memos.
Unit 3 Sales – A/R (Account Receivable): In this unit
Overview of the Sales Process:
• Sales Order Delivery A/R Invoice Incoming Payment
Sales Order to Cash :
• Perform the steps in the sales process from sales order to cash
• Describe the effect of each step on inventory and accounting

Customers:
• Define a customer group
• Create a new customer
• Create a lead
• Convert a lead into a customer

CRM(Customer Relationship Management)
• Activity Sales Opportunity Sales QuotationSales Order Delivery A/R Invoice Incoming Payment
Automating Sales Processes
• Availability checks
• Pick & Pack List.

Returns and Exchanges:
• If any item is Damage than we used Return or Exchange scenario.

A/R Credit Memos:
• The A/R credit memo (or credit note) is the document used to process returned items or to give a pricing credit, once an A/R invoice has been issued.

Unit 4 Items: In this unit
Item Master Data
Defining Item Groups
Units of Measure
Valuation Methods

Unit 5 Inventory: In this unit
Warehouses
Goods Movements
Serial Numbers and Batches
Physical Inventory
Unit 6 Pricing: In this unit we covered.
Pricing Concepts
Price Lists
Period and Volume Discounts
Special Prices for Business Partners.

TB Training Accounting TB 1100:
In this training are five unit.
Unit 1: Accounting for Sales and Purchasing
Finance Basics
Business transactions and values exchange
Financial Settings
Automatic journal Entry value

Unit 2: Banking Process: In this unit
Handling payments: incoming and outgoing
Payment Means
Deposits
The Payment Process in SAP Business One
Working Methods
The Payment Wizard
Unit 3: Financial Process : In this unit basic functionality of finance module
Define and manage the chart of accounts, the chart of accounts structure, Default G/L accounts
Journal Entries file and the Journal Entry Form, Reverse Transactions
Posting Tools -Posting Template with Percentages, Recurring Postings, Journal Voucher
Unit 4: Posting Periods Process : In this unit
Define periods and post transactions, Internal Reconciliation Definition, System Reconciliations, Full and Partial Reconciliation, User Reconciliation, Reconciliation Currency, Period End Process Period-End Closing Utility, Posting Period Status
Unit 5: Controlling Reports: In this unit is various finance Report like Balance Sheet, Trial Balance, Profit and loss, statement of cash flow, cash management report.
Unit 6: Additional Financial Topics: In this unit we covered all currency like system and local with different system test scenarios. Exchange Rate, Conversion difference and Fixed Asset.

Base tables versus target tables

Base tables and target tables are special linked tables within SAP Business One. They are the most often used linked tables for SQL queries too.

You may find most of them related to "Sales-A/R" and "Purchase-A/P" documents or so-called "Marketing Documents".

Marketing documents may not have base tables or target tables. From the previous screenshot, you could clearly find that the Base Document and Target Document are available to this Sales Order. To get the Base Document, you may click on the "left arrow icon" or use the shortcut key Ctrl+N. To get the Target Document, you may click on the "right arrow icon" or use the shortcut key Ctrl+T. Only when the base table or target table is available to the current document, will you find the menu items and icons in active status. Otherwise, both icons and menu items are grayed out.

From the terms "Base" and "Target", it is clear that the target table can be based upon the base table.

One table could be based on different types of tables:

From this demonstration, you could get a clear picture about the relationship between Base Document (table) and Target Document (table). A specific pair of Purchase Order and Good Receipt PO tables is shown here. This concept applies to all document type tables. Here is a list of commonly used base-target pairs; they are not inclusive. You may find more, but the following are the most frequently used ones:

Base Table	Target Table
OQUT-Sales Quotation	ORDR-Sales Order
OQUT-Sales Quotation	ODLN-Delivery
OQUT-Sales Quotation	OINV-A/R Invoice
ORDR-Sales Order	ODLN-Delivery
ORDR-Sales Order	OINV-A/R Invoice
ODLN-Delivery	ORDN-Returns
ODLN-Delivery	OINV-A/R Invoice
ORDN-Returns	ORIN-A/R Credit Note
ODLN-A/R Invoice	ORIN-A/R Credit Note
OPOR-Purchase Order	OPDN-Goods Receipt PO
OPOR-Purchase Order	OPCH-A/P Invoice
OPDN-Goods Receipt PO	ORPD-Goods return
OPDN-Goods Receipt PO	OPCH-A/P Invoice
ORPD-Goods return	ORPC-A/P Credit Note
OPCH-A/P Invoice	ORPC-A/P Credit Note

I have omitted the details for the link. Actually, you will find that all the links exist on the first child table or so-called row table for the header table, such as QUT1 instead of OQUT.

The linking fields are very clear. For example:

·         BaseEntry in the target table refers to the base table's DocEntry

·         BaseType refers to the types of the base table

·         BaseRef is usually linked to DocNum field in the base table

·         BaseLine will be the line number in the base line table

·         TargetEntry in the base table refers to the target table's DocEntry

·         TargetType refers to the types of the target table

Keeping it simple—The key to build a good query

Simplicity is in need everywhere in the current changing world. Wherever you make things complicated, you may find yourself in an awkward position to compete with others.

My slogan is: simple, simpler, the simplest.

I have a habit in query building: the last step for any new query would be checking to see if it is the simplest one. In this way, "keep it simple" would not only be kept in the already built query, but also helps new queries to be the simplest in the beginning.

By keeping a query as simple as possible, it will ensure that the system performance is not affected. It will also be a great help to the troubleshooting process. A short checklist for simplicity is as follows:

·         Other queries: Are there any other queries doing a similar job, and if yes, why does the new query need to be built?

·         Tables: Are there any tables that have not been used for the query?

·         Fields: Are there any fields that have not been used for the query?

·         Conditions: Are there any condition overlaps?

The list can be much longer. The meaning behind it is clear: there is a never ending battle to get rid of complications.

When you try this method and it becomes a routine, you will find that query building becomes an enjoyable process.

Date Deviates from Permissible Range SAP Business One

In running our business we face problems just like you do when using SAP Business One. Just today, fresh from creating posting periods for next year, our financial people were asking about the error "Date Deviates from Permissible Range" when adding a document. These documents had a due date of next year, so we were in essence using the freshly created posting periods for 2014.

The problem lies with the due dates and the default settings for creating posting periods. Very often you will have documents that require a due date that crosses the year threshold. For example in November you need to create an A/R invoice to bill a customer in January of the next year with 90 day terms.

The solution is changing the current years posting periods to be allowed to post outside of their year. This typically only affects the months of November and December and sometimes October too. So we will have to dig in and change those posting periods.

Posting Period Settings

Navigate on the main menu to:Administration -> System Initialization -> Posting Periods. Click on the yellow arrow next to the posting period of November of your current year. You'll see that the due date expressly allows up to 12/31/2013. If your customer has 60+ day payment terms this will prevent documents being added to the system while giving the "Date Deviates from Permissible Range" error.

Fixed Posting Period

To fix this issue, as a matter of course, change the "Due Date From" ending date in the months of November and December in all years. We recommend setting the date to at least March of the following year to prevent problems. With the posting period now fixed, you will be able to add documents with due dates that push into the next year.

Also, keep in mind that posting periods cannot be removed once transactions have been posted to them. If you have created posting periods with the idea of going back later to fix some things, please make sure you do this before you allow any postings into the next year.