SAP EWM Drive for Consultants, Also SAP server access for MM/SD/PP/QM/EWM/S4 Hana - Technical and Functional
Click on this Image and subscribe to YouTube Channel to get free SAP EWM documents like BBP, FS, etc
Click on above picture and Subscribe to YouTube Channel(Madhavi‘s Kitchen) and send email to get free SAP EWM S4 documents(BBP, FS, Technical specs, Functional specs and others - Studyuuusapewm@gmail.com
Import Procurement full overview explanation •Procuring
of goods from US to India or any other places India to USA •Currently
India is using GST, so there are no different condition types will trigger •Whereas
in case of different country, the condition types for customs will come into
picture •Remove
the tax code or maintain it to 0% and maintain the vendor to unchecked GR based
IV
•Customs
Clearance vendor will be different/Same as per the company requirements
•But
if the customs vendor is different then IV needs to be posted before GR and
that should be paid
•Once
material received to plant then GR and following with IV will happen
•Orders
or u can use even same normal doc type(Preferred to use different)
•Material
master—Foreign trade import tab –Fill details what type of products /region and
Origin
•Vendor
master—remove the GR based IV check for vendor or Invoice tab
•Check
calculation schema whether import condition are maintained to calculate charges
in PO
•Perform
PO with all the details and do the Invoice with planned delivery costs
•Now
perform the Goods receipt and Invoice receipt for normal goods
•Payment
will release to vendor and prior payment of customs will be processed to
vendor.
Basic
Concepts to learn before learning Partner profile:
·Concept:
IDOC
is an intermediate document where many industries will use to transfer their
data from one system to other system, it can be SAP to SAP or SAP to Non- SAP.
As an SAP MM consultant,
we will work less on IDOC’s, but we should know the concept behind the IDOC for
resolving the issues by Monitoring the IDOC.
·Overview:
IDOC is an SAP object where data will be transferred inflow and outflow through
electronic message, the main use of IDOC is transfer of data from SAP to Non-SAP
through EDI and SAP to SAP through ALE.
Here we have
2 types of flows in SAP, where data will be flowed into SAP and other is data
transfer to other tool from SAP through Inbound and Outbound.
·Inbound:
Data that received from other tool to SAP in the form electronic message.
·Outbound:
Data that will be flowed to other systems through SAP in terms of electronic
message.
We have 2
IDOC types
·1.Basic Type- It
sends the information to the receiver port as per the mapping fields done by
us.
·2.Extension- When
we want any extra information to send to receiving party then we have this IDOC
extension.
Conversion
Format:
If data is transferring SAP to Non-SAP then data
format is required that EDI acts as a data converter, it converts data to XML
format and loads the data and sends to another tool respectively.
Mapping of
fields has been done as per the size and data fields.
Mapping is
same as LSMW method and it will be done by MM technical consultant and as a
functional consultant we need check the port number and few major things
explained below.
**** we
have segments, where fields will be stored in the segments and mapping will be
done according to the segments available in the IDOC****
We have
Parent segment and Child segment; different fields will be stored in different
segments.
Note: IDOC
direction explains whether the data is flowing inbound or outbound.
Partner:
We have 3
partners in SAP R/3, where data will get exchanged within this and they are
LI-Vendor, KU- Customer, LS- Logical system.
Vendor-
Normally we use work with vendor for PO, Order confirmation, Order
acknowledgement and Invoice.
Customer- SD
side, Sales order
Logical
system- we have other department systems, where weight lift measuring tool.
Data flows
inside and outside as per the above examples.
Port:
The port we
maintain it contain IP address of the source or receiving system and this port
number will be provided by Basis Consultant.
ØPartner Profile maintenance:
Partner
profile should be maintained for all business partners where if we want to
receive/send information to all the vendors.
T-code to
maintain the partner profile is WE20.
Double click
on partner and click on LI-vendor, if we are setting partner profile with
vendor.
Once we enter
on vendor, we can see above screen where we can have options to enter inbound
and outbound entries, as I told this will be electronic message where data
flows.
We have
message type in which we see inbound or outbound and, we can see contact information.
·Select any of the two – either
inbound or outbound
And system
will ask for receiver port number and this will be given by Basis consultant
and here every filed is mapped and after they will provide the receiver port
number to maintain in the below screen.
2.Next tab-
Message Control:
If we are
sending PO copy, we have message type for PO, insert message type and enter the
link code ME10.
Whenever PO
copy is created for this message type then IDOC number will be generated and transferred
to receiver.
Change
message: In message control we can see change message
option where if there is any change in document the IDOC will sends the changes
automatically for that we need to maintain 1 more line in message control with
change indicator.
3.Inbound
options- Inbound Parameters:
Here we need
to select the trigger by background program, so that it will take the
parameters after saving and as per mapping it will send to receiver
automatically.
4.Post
processing:
Here we will maintain
the agent who should receive the notification when EDI processing fails, System
will send the log data and reason for failure.
5.Telephone:
We can enter the telephone number of
receivers.
6.EDI
standard:
Here we can
update the message type as per the purchase order.
Overview Explanation of above everything:
*****
Receiver port
means – the receiver IP address or data that is mapped and created a port that
is receiver port.
We have IDOC
type where it contains the segments in which it mapped all the fields, we will
maintain the idoc type in outbound and it should be purchasing/sales
Once we have
IDOC type, we had message type where what kind of data that is transferring or
mapped it can be purchase order, Acknowledgement, Contract.
Process code
– where we have message type and idoc type contains the sending data
information, now to process this we need some code that is process code.
By above 3
Idoc will trigger and sent to receiver
. ******
ØIDOC Structure and records-
Monitoring of IDOC:
IDOC
structure is divided into 3 records.
1.Control record
2.Data record
3.Status record
1.Control
record:
Control records contain few data like.
IDOC
number
Direction
of IDOC
IDOC
Status
Basic
type
Receipt
information
Sender
information
Port
number
2.Data
record: Contains data that flows through EDI
Data
record will have segment and child segments
Each
segment will have some data with fields and as per segment the data will flow
to receiver.
3.Status
record:
we can find the status of IDOC processing:
We
can find the PO’s processed with help of IDOC, whether its inbound or outbound.
For
outbound idocs- 16 is the number for success
For
inbound idocs- 53 is the number for success
---if
we get error then want to find the idoc number in PO, then go to attachment tab
in PO and click on relationship.
Tickets
and Questions related to IDOC’s
How to monitor the IDOC?
Answer:
T-codes IDOC
WE31- Create IDOC Segment
WE30- IDOC Type
WE20- Partner Profile
For
this partner what type of information we are sending to receiver.
WE02- Monitor the IDOC
WE05- List of IDOC’s
WE21- Delete the IDOC
WE19- Testing of IDOC
Customized T-code- Status change.
Manual processing of IDOC – BD87
WE09- Searching for specific information like
PO
45.1 Why do you reprocess IDOC?
All failed IDOCs should be reprocessed for the
confirmation of output messages to vendor
We have own tcode for reprocessing the IDOC
IDOC Statuses?
1-50
will represent the outbound status
03- IDOC has been triggered
16-Succesfully generated successfully
51- 78 will represent the inbound
status
53-
Successfully posted inbound
59- IDOC error
All Error Status:
02- Error transferring data to port
04- Error in EDI information
05- Error during conversion
45.2 Frequent IDOC errors.
1. When the receiving info mapping has
required fields and sending info is missed that data, then IDOC failure will
happen.
2.When they edit PO and reprocessing
the IDOC, then IDOC will gets failed as IDOC will trigger automatically.
3.Failed to transfer data to port,
its error from BASIS side, where data is not able to reach the port.
4.when there is an application type
mistake was happened then also EL is for contract and EF is for Purchase order.
For all IDOC errors we need to change
the status manually to status 30- ready for shipment- We have customized tcode
for changing the status.
5.with the same order number IDOC
receivers one more output then IDOC will gets failed with status 59.
Question: What
is IDOC? IDOC is an Intermediate document,
where data will be transferred and received into the receiver system with the help
of EDI.
OR Data exchange between two systems can
takes place with the help of IDOC as per the requirements We have 2 methodologies in IDOC, one
is ALE IDOC and other is EDI IDOC.
ALE IDOC will be data transfer between SAP to SAP system.
EDI
IDOC is data transfer between SAP to NON -SAP System
Explain the setup of IDOC- Inbound or Outbound:
We will setup the IDOC, as once we get confirmation
that with whom data transfer is going on.
1.vendor- LI
2.Customer-KU
3.Logical system- LS
Any data that transferring out of our system to other
system is called outbound
Any data that transferring into our system to other
system is called Inbound
·Setup
of IDOC for Vendor:
WE20- we will select the vendor and enter the vendor
number and few fields will fetch automatically like partner type and agent.
We can see 2 options Inbound and Outbound, select the respective
one and enter the partner role and message type.
Now system will allow us to maintain the receiving
port number, which will be given by Basis consultant and enter pack size
and basic typeof IDOC and extension
1.What is Port number
Port number contains the receiver
details where we are sending the information to the partner, Port number
contains the IP address of the receiving partner to flow of data.
2.What is Basic type
Basic type contains the data where it
should flow to receiver and data will flow with the help of segments.
3.What are Segments
Segments are the part of IDOC, where
all the fields mapping will be done like item details and header details wrt
receiver system, in which every segment like few fields and it will help to analyze
the data also.
4.What
is Extension:
In Basic type we are sending data as
per the mapping done in segments, few cases we have some customizing fields
that needs to be transferred to receiver then it should be done by extension field.
·Once
we complete the above details, we have message options to setup, here we are
mentioning application and message type along with process
code
1.What is Application
Its code where we will select as per the purchasing document, EF for
purchase order
2.What is message type:
It
explains what type of message we are sending to the receiving partner, like we
will send PO, Invoice, OC and Acknowledgement
3.What is Process code:
It’s a piece of code, where we have mentioned segments for fields and
sending PO through electronic message and now ABAP team will prepare a code for
that message.
·Once we are done with this now, we
need to maintain the agent number- Respective buyer number in post processing,
where IDOC status will be generated and flowed to buyer and he will analyze the
OCR.
How do you Monitor an IDOC?
WE02- we will search for the IDOC and we see the
records maintained for that IDOC.
1. Control record
2. Data record
3. Status record
Control record: Control
record contains the information of IDOC number, who is the receiver/Sender and
IDOC created on and few more basic details
Data record: It contains
the segments, where we mapped few fields and if any field in not popping up,
then we will check in this record and ask ABAP team to add those fields.
Status record: Where we
can see all documents processed for that IDOC, we can check PO number and we
can see access sequence number wise.
We can have number like 53 for successful outbound and
13 for successful inbound.
Manual Processing:
We can have selection like whenever PO is saved IDOC
will get generated, if not we can mention as collective IDOC and send those manually
by T-code BD87
Failure IDOC:
We can have few failure messages through IDOC,
We have 2 separate programs, where IDOCs will be
processed again.
Test IDOC:
If we want to test and edit the IDOC, then we have
test IDOC, where we ca copy by tcode WE19 and edit and test the IDOC- Only for
testing.
